Comments (11)
Hi @WardCunningham, instead of improving a centralized federation search service, I'd propose to investigate distributed search and caching backends which would offer a first step towards a resilient wiki search service. Would it make sense to compile a list of candidates, or would an approach favouring implementation over theoretical discussion avoid such a step?
from wiki.
yes - let's start researching how to do this - I've made a provisional index of search tools that we might be able to use - some Node based ones and some open source alternatives to Google site search - also some notes on sitemaps here - http://future.fedwiki.org/search-research.html
from wiki.
@almereyda I agree. I suggest moving forward with this code in order to create the demand for a better version. How this might work would be discussed in issues under wiki-plugin-search.
I see little point in improving a centralized search as it will discourage building a distributed search that would enhance the notion of neighborhoods. I've described one vision for how distributed search could work.
http://ward.asia.wiki.org/view/distributed-search
The feature I describe as 'more' is implemented in fedwiki/wiki-client#132 which I would like to explore in practice.
Since starting this project I have become familiar with the awesome capabilities of ElasticSearch. I also note that ElasticSearch as a service is available at about $40 a month. My personal goal for search is to make a distributed version that outperforms any centralized version by making its incremental nature a feature. ElasticSearch is plan b.
from wiki.
"I suggest moving forward with this code in order to create the demand for
a better version."
I feel intruiged, but once again in the same time well-taught by this
blatant example of what some people started half of my life ago:
http://agilemanifesto.org/
Will need some decommercialized reframing in words, yet mere practice
remains.
On 24 November 2015 at 17:11, Ward Cunningham [email protected]
wrote:
@almereyda https://github.com/almereyda I agree. I suggest moving
forward with this code in order to create the demand for a better version.
How this might work would be discussed in issues under wiki-plugin-search.I see little point in improving a centralized search as it will discourage
building a distributed search that would enhance the notion of
neighborhoods. I've described one vision for how distributed search could
work.http://ward.asia.wiki.org/view/distributed-search
The feature I describe as 'more' is implemented in fedwiki/wiki-client#132
fedwiki/wiki-client#132 which I would like to
explore in practice.Since starting this project I have become familiar with the awesome
capabilities of ElasticSearch. I also note that ElasticSearch as a service
is available at about $40 a month. My personal goal for search is to make a
distributed version that outperforms any centralized version by making its
incremental nature a feature. ElasticSearch is plan b.—
Reply to this email directly or view it on GitHub
#69 (comment).
from wiki.
I think as a rule, I would like the repos for plugins that are part of the standard wiki distribution to in the fedwiki GitHub organization. Of course, the necessary GitHub organization configuration will be done such that the person contribution the repo retains write access.
For npm, it would be good to add the core
team as owners - using npm owner add <user> <package>
with the current team being ward
, nrn
and paul90
.
In the meantime, as you know, the search and transport plugins have been included in the latest wiki distribution.
from wiki.
whoops, clicked the wrong button 😊
from wiki.
Yes, absolutely agree.
Perhaps the documented procedure should go something like this:
- Contributor authors plugin, github repo, npm module.
- Contributor posts issue to wiki repo offering plugin for evaluation.
- We publish beta version of wiki with plugin included in package.json.
- Community evaluation discussed in issue, Contributor responds.
- Contributor transfers ownership of both repo and npm package.
- We release semantically versioned update of wiki.
If this sounds right, I will get caught up with the ownership transfer and revise the contributing doc.
from wiki.
Sounds good
from wiki.
How can we confirm that contributions adhere to our conventions? I depend on @paul90 to tweak build scripts and package versions but this doesn't seem right. One simple approach would be to include an industrial strength version of mkplugin.sh in the repo and keep its build and package.json up to date. What do other projects do?
from wiki.
That is one option, the other would be to have a template repository using a tool like grunt-init
from wiki.
Ok, I'll look at grunt-init. Thanks for the tip.
from wiki.
Related Issues (20)
- Login with google broken on subsites in fed.wiki.org HOT 2
- Docker container fails to start failing to find coffee-script module HOT 12
- Quickly accessing many farm sites after daemon boot up crashes server HOT 4
- Installing federated wiki on cPanel node.js HOT 18
- Swiping on smartphones and tablets HOT 4
- Search field in window footer, search link in page footer HOT 4
- How does Federation work? HOT 3
- Is my site visible in the federation? HOT 2
- Wiki pages can run out of memory and lose precious content due to images HOT 8
- Feature request: support interoperation over ActivityPub HOT 4
- Cursor does not stay in HTML form HOT 8
- Installing Graphviz plugin HOT 2
- Don't create ~/.wiki without asking first HOT 2
- Testing Graph Plugin [ParseError] HOT 1
- missing CSS HOT 9
- Wiki pages with a long list of wiki links stopped paginating correctly? HOT 6
- How can i create wiki page with wiki markup HOT 1
- Internationalisation (i18n) HOT 10
- Internationalization of page titles HOT 8
- Automating releases, building and publication of package artefacts HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wiki.