Bottiger, Wait and see. Don't give up just yet. You may find a diamond in this lump of coal yet.
While it may seem like you won't be able to contribute, it is quite the contrary. You will be able to join forces with others making similar contributions and go on to do great things together. The developers deserve the same. But it would not be useful to have our conversations regarding what to fix that is not code-related be intermingled with the developer chatter. I personally don't care what they are working on, but I do care about the site, and documentation, and other non-coding issues. I personally have no interest, currently, in contributing code (mostly because I don't know what to contribute), but I do know other things to contribute. I want a place where I can discuss with others like you and I, and work together on something big. I also don't want to flood the users group with this discussion. Imagine making a post about a question, and having your post end up on page 2 where no one will see it because of other messages related to 80/20 discussion and roadmap, and all sorts of MANAGEMENT issues. I would be pretty pissed, don't know about you. All I want on the users group is to get an answer to a simple question. I don't care about road-maps and those things. When I want to read that, I will happily go into the web2py group that is specific to those topics. On Jul 18, 1:21 pm, Bottiger <[email protected]> wrote: > I can't shake the feeling that I spurred this move. > > I might be a newcomer to Web2Py, but I have already sunk some time > into studying Web2Py such as finding broken links on the main page and > benchmarking the bundled version of flup (which should not be used in > a production environment because of GIL) compared to the official flup > that has prefork. I have had made code contributions to other open- > source projects, and I planned to for Web2Py but now it is looking > more difficult. > > On Jul 18, 10:34 am, Joe Barnhart <[email protected]> wrote: > > > I am surprised at this division of groups. Web2py does not have so > > much traffic that it is a burden to have all messages in one group. > > The intent is *precisely* to exclude people from certain > > conversations. There really can be no other reason for setting up a > > "developers" group with gated write access. The answer to "certain > > comments taken out of context" is more and better communication, not > > restricted lists of high priests vs. commoners. > > > This strikes me as very heavy-handed and autocratic. This is not a > > good sign for our project. You have set the barrier for participation > > in web2py very high by this move. Honestly I am very surprised that > > anybody (esp. Massimo) thinks this is a good idea. > > > Warm regards, > > > Joe Barnhart > > > On Jul 17, 5:39 pm, mdipierro <[email protected]> wrote: > > > > One more thing... this is not at all intended to exclude people from > > > important conversations. > > > > If you feel one way or another you can still bring it up here. > > > > It is just that sometime some comments may be taken out of context > > > from new users and be interpreted in the wrong way. > > > > Let's see how it works out. If you have any suggestion to improve let > > > me know. > > > > Massimo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
