Improving Federation
L3MNcakes
Public
Seen by 101
It seems like we are throwing an awful lot of feature proposals on the back-burner due to a need to improve the Federation protocol. In contrast, I have seen little to no discussion on actually improving Federation. I started this discussion hoping to change that.
Perhaps we could start by:
Identifying all the problems with Federation that are currently holding us back
Combine these into an easy-to-read document/wiki article so new developers can get a better a sense of what is going on (and probably be more able to contribute! ;)) and more experienced developers can have a single document to reference while brainstorming. (If there's not somebody on the "Documentation Editors" team that wants to do this, I will happily volunteer.)
Establish an open team of developers who would like to collaborate and solve these complex problems. (Count me in!)
Please chime in with your thoughts. The above course of action is merely a suggestion, so if you have a better idea on how to approach this, please share!
Nick Sun 16 Jun 2013 9:26PM
ok, sorry just saw that separate discussion and it seems to be something that has been agreed on pretty unanimously. Ignore comment!
Flaburgan Mon 17 Jun 2013 9:28AM
@nickdowson no problem ;)
Poll Created Tue 25 Jun 2013 5:57PM
First Step : Separate Federation Layer Closed Wed 10 Jul 2013 12:00AM
I would like to propose that we move forward in improving federation with a first step of separating federation into it's own layer. This would involve :
1) Forming a working group of developers/collaborators who would like to volunteer their time to this problem. I think it's important to have a defined (though very much open) group dedicated to this problem, because simply leaving it open for an individual to pick up and run with leaves me with the feeling that it's simply going to never get done.
2) That group would come up with detailed plan for separating out federation and any potential problems that might arise. Communication can be done through IRC Meeting/Email Chain/Loomio/whatever works best for the people involved. The goal here is to produce an organized document that can be easily understood by newcomers who want to jump in and help out as well as a reference for those involved to ensure everybody is on the same page with what exactly needs to be done.
3) Plan could be verified/approved by other developers/collaborators through Loomio. (Maybe this step isn't necessary, but I think it's always a good idea to get outside opinions before implementing a plan.)
4) Plan is broken down into manageable tasks and put into Github where developers can pick them up and begin making code changes.
Results
| Results | Option | % of points | Voters | |
|---|---|---|---|---|
|
|
Agree | 100.0% | 13 |
|
| Abstain | 0.0% | 0 | ||
| Disagree | 0.0% | 0 | ||
| Block | 0.0% | 0 | ||
| Undecided | 0% | 134 |
|
13 of 147 people have participated (8%)
goob
Tue 25 Jun 2013 6:36PM
We already have agreement to separate fed into a layer - https://www.loomio.org/discussions/612?proposal=463 - and I agree your practical steps would be an excellent way to go about it.
Elm
Tue 25 Jun 2013 6:47PM
Good way to go !
Nick
Tue 25 Jun 2013 8:52PM
great plan!
Rasmus Fuhse
Wed 26 Jun 2013 9:53AM
Yeah, that's important!
Sean Tilley
Wed 26 Jun 2013 7:24PM
This is great, but I think the bigger issue here is not a matter of want, but rather a matter of developer muscle and resources. Federation is pretty complex, and so our federation system needs to be fully documented and studied.
Seth Martin
Thu 27 Jun 2013 8:01PM
I can't think of anything more important for this project.
Nick · Sun 16 Jun 2013 9:24PM
@flaburgan - as a non-techy, what would separating the federation from the rest of the code involve?