Hi Marco, that's great news! Thank you for the support!
Greetings, Oliver Am Montag, 19. November 2018 23:27:04 UTC+1 schrieb marco.cappellacci: > > Hi community! > > I totally agree with you Federico. > I'm glad to inform you about that: > The University of Urbino, the organization I work for, will provide a > virtual machine to install discourse. > I'm working on It! > > > > Il giorno dom 18 nov 2018 alle ore 14:40 Federico Capoano < > [email protected] <javascript:>> ha scritto: > >> I'll try to be brief because I don't want to use too much of your time. >> >> The community is growing and some of the ways which were working up to >> now are not working so well anymore. >> >> Here's how I propose to address the issues, let me know what you think. >> >> *Git repositories: branch protection and write access* >> >> 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. >> >> The core development team on github will be "liquid", we can add new >> active contributors and remove contributors who are not active anymore >> often. >> >> *Discussions* >> >> I'm not sure that as we grow this mailing list is the best tool to >> communicate. Sure it's comfortable for me but I'm not sure for new >> contributors if it is so for the following reasons: >> >> - many people are receiving all emails and as the volume of discussion >> increases many will most probably stop reading or unsubscribe >> - some new subscribers are not used to mailing list and are probably not >> aware of the fact that they should limit their communications to the bare >> minimum >> - I believe some users/contrbutors are mainly interested in one specific >> area of OpenWISP and would probably prefer to receive updates of new >> discussions that are only relevant to that area >> >> That's why I'm starting to consider the option of using discourse >> <https://www.discourse.org>, which seems to be working well in the >> OpenWRT community (and other communities as well). >> >> 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. >> >> Best >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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.
