On Sun, Nov 18, 2018 at 9:53 PM Oliver Kraitschy <[email protected]> wrote:
> Hi Federico, > > > On Sun, Nov 18, 2018 at 05:40:44AM -0800, Federico Capoano wrote: > > > > I just implemented the following change: most of the important > repositories of > > the OpenWISP 2 modules and documentation have their master branch > protected to > > avoid accidental damage. > > > > I added a core development team on github which has write access to most > of > > these repositories but won't be allowed to push to master without going > through > > a pull request review. > > Does every PR have to be reviewed by you or can members of the core > development team review each other's PRs? Just thinking about the load on > you :-) > At the moment I think any core dev can review but only admins or specific people can merge. For example, you have permission to merge in the openwisp-config repo. As some contributors specialize in some repositories I want to distribute the responsibilities more and more. I just want to be sure everyone that gets to that point understands how important it is to properly review, test and improve patches because I know from experience that merging patches in a lighthearted way can lead to unexpected problems and bugs in very bad moments, eg: usually while we are traveling, busy with personal issues or worse on vacation.. > > The core development team on github will be "liquid", we can add new > active > > contributors and remove contributors who are not active anymore often. > > Thank you for adding me - I'm feeling honored once more :-) > You deserve it. > [Disadvantages/shortcomings of the mailing list] > > I agree with all the things you said. > > > That's why I'm starting to consider the option of using discourse, which > seems > > to be working well in the OpenWRT community (and other communities as > well). > > I have no experience with Discourse but it seems to be the best forum > software out there. I did some investigation for such a software some time > ago and Discourse seemed to be the best choice. Unfortunately it's only > available as a docker image. > One thing I forgot to add, discourse allow replying via email, so for those who like mailing lists it should change much. > > This change would likely require time before we implement it correctly. A > > considerable amount of work would be needed to do it, not just because > we'd > > have to install and maintain a discourse instance, but also because this > change > > should be reflected in the website / documentation, users would have to > be > > imported (not sure how that plays out with privacy regulations), the > structure > > / categories and rules of the eventual new discourse instance should be > created > > before completing such a move. > > Would you host the instance somewhere yourself or let somebody else do the > hosting? I'm just thinking about the obligations which come with hosting > such a platform. > I would have liked to buy it but the price is not cheap (entry level is 100 USD / month) so I think for that price it's better to host it at the moment. An option would be to not migrate the user accounts but to ask users to > register at the new forum if interested - that would also clean up the > userbase. > The first thing I have to do is to find out if it's ok to contact each member to communicate this change. If we can, we can either just ask them to subscribe to the new platform, or we could tell them we are going to migrate and if they don't want to be migrated to let us know so we can remove them. Federico -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
