On Fri, Oct 7, 2016 at 2:27 PM, Bruno Souza wrote:
> There is another thing also: the sentiment of belonging. We are a separated > community, and the more we insist in do what we always did (we start with > domains and mailing lists, but pretty soon we will be wanting to keep our > processes and more...) the harder will be for us to accept belonging to > Apache and be accepted also. Agree absolutely -- and also with the earlier comments in this thread by Hermien and others. The defaults, we'll take them -- and see as we go from there. And this discussion is great, I really like the Apache approach of discussing and reaching consensus [or, beating a topic to death, maybe] in this way. The more we discuss, the more aligned we're becoming. Gj On Fri, Oct 7, 2016 at 3:37 PM, Wade Chandler <[email protected]> wrote: > On Oct 7, 2016 8:39 AM, "Emilian Bold" <[email protected]> wrote: > > > > > There is another thing also: the sentiment of belonging. > > > > This is a really good point Bruno. > > > > My point is that it's much simpler for contributors to join Apache. We > just > > use another mailing list, use another repository URL for commits, etc. > > > > But, we have 1.5 million users. And the website, the forums, the mailing > > lists, the wikis are for them too. And we have to do this transition > really > > well. > > > > All of this is IMHO... > > I agree with this. I think the points Bertrand and Bruno make are spot on, > but we have to transition well for the users or IMO it won't be a success, > and with that many it can be hard. > > I do think giving notices and transitioning people will work however. I > think as has been stated by Gj, let's get the base lists up, and the Wiki, > then we can get docs up, those help users, even finding lists, processes, > etc. Then the static site. At the same time dev starts to happen on the > Apache lists. The users continue where they are. > > Once the site and wiki are here, we can link to where downloads are etc, in > the interim, and start to redirect things here (Apache). Then the code > migration and development processes can be phased in as that really looks > to be the most difficult part to me per the repository talks. > > All the while, we can redirect users to come here for lists, and add a > header notice or something to all NetBeans.org mailing lists while those > lists continue to work, and then for a period there will be a dual reality > Apache and NetBeans.org mailing lists. One day those NB.org lists auto > reply they are no longer where users should go, and their message will not > be delivered. I think by the time that happens most will have moved over. > After that, they certainly will, and is about as seemless as one can hope. > > Wade >
