So I take this as a go for the re-org of wiki per release. 1. It will give the community a better view of the feature designs. If someone prefers a google doc, please do so and make that info available on this wiki via link.
2. In the 1.99.4 I updated a lot of the docs (.rst), Even though I am not a big fan of the format we are using, Having feature complete guides in one place in .rst is what I recommend as well Having said that, if someone wants to write an extensive guide/ blog posts / some technical chops related to the feature they implemented, please feel free to link them off this wiki. I will have a section for papers/ presentations/ blog posts to do that. Best, *./Vee* On Tue, Nov 25, 2014 at 8:14 AM, Jarek Jarcec Cecho <[email protected]> wrote: > That seems as a good suggestion Abe, we can collaborate on the design on > shared platform. We can use the Wiki as was suggested or something like > google docs where I see slightly better ability for adding comments to > specific parts. I don’t have personally strong opinion about either. > > When the feature is done, we should definitely provide final documentation > to the code base, so that we can version and release it with the rest of > the code. > > Jarcec > > > On Nov 24, 2014, at 10:12 PM, Abraham Elmahrek <[email protected]> wrote: > > > > Just a thought. Let's put design docs/proposals on the Wiki and docs in > the > > code base? > > > > On Mon, Nov 24, 2014 at 7:26 PM, Veena Basavaraj < > [email protected]> > > wrote: > > > >> Richard, > >> > >> thanks for your inputs. The way kafka project does it, for every > release, > >> with sufficiently large feature such as Kerberos or increment read/ > write > >> support, they put up the design wiki and colloborate. > >> > >> If you see this wiki, > >> https://cwiki.apache.org/confluence/display/KAFKA/Dynamic+Topic+Config > >> > >> you can also see comments, discussions etc. > >> > >> So unlike in PDF, it is easy to provide comments and clarify question > >> regarding the overall design. > >> > >> > >> > >> > >> Best, > >> *./Vee* > >> > >> On Mon, Nov 24, 2014 at 6:44 PM, Zhou, Richard <[email protected]> > >> wrote: > >> > >>> +1, it's a good idea. And I could add guide of Kerberos support on > >> Sqoop2. > >>> > >>> -----Original Message----- > >>> From: Veena Basavaraj [mailto:[email protected]] > >>> Sent: Tuesday, November 25, 2014 10:41 AM > >>> To: [email protected] > >>> Subject: Re: sqoop confluence wiki > >>> > >>> resending again.! > >>> > >>> On Mon, Nov 24, 2014 at 4:46 PM, Veena Basavaraj < > >> [email protected]> > >>> wrote: > >>> > >>>> Hey all, > >>>> > >>>> I am proposing to give some TLC to our wiki. > >>>> > >>>> https://cwiki.apache.org/confluence/display/SQOOP/Home > >>>> > >>>> Its been a while this wiki has been re-orged. Lot has happened in the > >>>> past few months in Sqoop2 and one of my suggestions was to have a good > >>>> list of design wiki for new features post 1.99.4. > >>>> > >>>> I would like to model the SQOOP a bit similar to how the Kafka project > >>>> has done it. ( Blatant copy infact !) > >>>> > >>>> https://cwiki.apache.org/confluence/display/KAFKA/Index > >>>> > >>>> Let me know if anyone has any reservations or feedback. > >>>> > >>>> Both are welcome! > >>>> > >>>> > >>>> Best, > >>>> *./Vee* > >>>> > >>> > >> > >
