Hello, Is there a consensus regarding the format of the documentation? I think RavenDB's documentation is a great example in terms of clear formatting and readability.
Ideas? Hadi On Tue, Jun 1, 2010 at 8:58 PM, Ayende Rahien <[email protected]> wrote: > I just sent Nathan Stott & Nathan Palmer the information on how to setup > the documentation. > If anyone else needs credentials, please ping me. > > > On Tue, Jun 1, 2010 at 4:54 PM, Nathan Stott <[email protected]> wrote: > >> Yeah, how do we get started with the documentation? >> >> >> On Tue, Jun 1, 2010 at 8:51 AM, Nathan Palmer <[email protected]>wrote: >> >>> http://github.com/rhino-etl/rhino-etl >>> >>> Also forked from ayende's account. Sounds like we're on our way. >>> >>> Where do we go to start getting the documentation setup? >>> >>> Nathan Palmer >>> >>> On Tue, Jun 1, 2010 at 7:36 AM, Corey Kaylor <[email protected]> wrote: >>> > http://github.com/rhino-esb/rhino-esb >>> > >>> > Now forked from ayende's account. >>> > >>> > On Tue, Jun 1, 2010 at 6:12 AM, Ayende Rahien <[email protected]> >>> wrote: >>> >> >>> >> inline >>> >> >>> >> On Mon, May 31, 2010 at 12:58 AM, Nathan Palmer <[email protected] >>> > >>> >> wrote: >>> >>> >>> >>> Oh yeah. I remember seeing something about that. Interesting idea. I >>> >>> like that you don't have the permission issues with this model. I've >>> >>> had problems getting TeamCity deploy a project to a different place >>> >>> that needed some enhanced credentials because it was running as a >>> >>> service. I will have to check this out. >>> >>> >>> >>> How do you want to proceed here? I'd like to start getting some >>> things >>> >>> setup for Rhino ETL.. getting the master repository out there, >>> >>> building on the build server, and starting to get some documentation >>> >>> out there on the site. So.. >>> >>> >>> >> >>> >> Please do :-) >>> >> >>> >>> >>> >>> Are you planning on creating the master repository or should I go >>> >>> ahead and create one and clone from yours? >>> >>> >>> >> >>> >> Go ahead and do it. >>> >> >>> >>> >>> >>> I'd like to get somewhat of a structured documentation setup and not >>> >>> necessarily just a blog post type documentation. Can we do that with >>> >>> what you have setup for hibernating rhinos? >>> >>> >>> >> >>> >> Yes, you can. >>> >> RavenDB's site is based on the exact same source. >>> >> >>> >>> >>> >>> Nathan Palmer >>> >>> >>> >>> On Sat, May 29, 2010 at 2:51 PM, Ayende Rahien <[email protected]> >>> wrote: >>> >>> > Texo >>> >>> > >>> >>> > >>> http://ayende.com/Blog/archive/2009/10/06/texo-ndash-my-power-shell-continuous-integration-server.aspx >>> >>> > Basically, you setup post notification in github, and it'll do the >>> >>> > rest. >>> >>> > >>> >>> > On Sat, May 29, 2010 at 10:18 PM, Nathan Palmer < >>> [email protected]> >>> >>> > wrote: >>> >>> >> >>> >>> >> Yeah. I like the named github idea (RhinoMocks/RhinoMock) >>> >>> >> >>> >>> >> What type of build server do you have setup for this? >>> >>> >> >>> >>> >> Nathan Palmer >>> >>> >> >>> >>> >> On Sat, May 29, 2010 at 12:26 PM, Corey Kaylor <[email protected] >>> > >>> >>> >> wrote: >>> >>> >> > Agreed >>> >>> >> > >>> >>> >> > Sent from my iPhone >>> >>> >> > On May 29, 2010, at 10:22 AM, Nathan Stott <[email protected]> >>> >>> >> > wrote: >>> >>> >> > >>> >>> >> > That would make the most sense to me as well. >>> >>> >> > On Sat, May 29, 2010 at 9:44 AM, sbohlen <[email protected]> >>> wrote: >>> >>> >> >> >>> >>> >> >> I agree -- that would seem to make more sense than the >>> all-in-one >>> >>> >> >> (or >>> >>> >> >> nearly-all-in-one) approach or an approach where each project's >>> >>> >> >> repository is intimately tied to a specific person's GITHUB >>> >>> >> >> account. >>> >>> >> >> This way if a change in project lead is desired (for any >>> reason) >>> >>> >> >> then >>> >>> >> >> there isn't the need to publicize a new GITHUB url for the >>> >>> >> >> project's >>> >>> >> >> master to the world. >>> >>> >> >> >>> >>> >> >> -Steve B. >>> >>> >> >> >>> >>> >> >> On May 29, 9:46 am, Ayende Rahien <[email protected]> wrote: >>> >>> >> >> > I am actually more in favor of creating separate projects for >>> >>> >> >> > each. >>> >>> >> >> > Like:http://github.com/RhinoMocks/RhinoMocks >>> >>> >> >> > >>> >>> >> >> > On Sat, May 29, 2010 at 3:15 PM, sbohlen <[email protected]> >>> >>> >> >> > wrote: >>> >>> >> >> > > What does everyone think about the idea of asking Lorenzo >>> if >>> >>> >> >> > > he's >>> >>> >> >> > > interested/willing to bring that source tree back into the >>> >>> >> >> > > 'fold' >>> >>> >> >> > > with >>> >>> >> >> > > the rest of the Rhino* projects and then manage it here >>> with >>> >>> >> >> > > the >>> >>> >> >> > > rest >>> >>> >> >> > > rather than having it continue to exist outside this >>> collection >>> >>> >> >> > > --? >>> >>> >> >> > >>> >>> >> >> > > Would there be value in that approach (for either users or >>> >>> >> >> > > maintainers) --? >>> >>> >> >> > >>> >>> >> >> > > -Steve B. >>> >>> >> >> > >>> >>> >> >> > > On May 29, 4:33 am, Ayende Rahien <[email protected]> >>> wrote: >>> >>> >> >> > > > Lorenzo Melato took ownership of that >>> >>> >> >> > >>> >>> >> >> > > > On Sat, May 29, 2010 at 5:52 AM, c.sokun >>> >>> >> >> > > > <[email protected]> >>> >>> >> >> > > > wrote: >>> >>> >> >> > > > > Ayende, look like we are missing Rhino-Common. >>> >>> >> >> > >>> >>> >> >> > > > > -- >>> >>> >> >> > > > > You received this message because you are subscribed to >>> the >>> >>> >> >> > > > > Google >>> >>> >> >> > > Groups >>> >>> >> >> > > > > "Rhino Tools Dev" group. >>> >>> >> >> > > > > To post to this group, send email to >>> >>> >> >> > > > > [email protected]. >>> >>> >> >> > > > > To unsubscribe from this group, send email to >>> >>> >> >> > > > > >>> >>> >> >> > > > > >>> >>> >> >> > > > > >>> >>> >> >> > > > > [email protected]<rhino-tools-dev%[email protected]> >>> <rhino-tools-dev%[email protected]<rhino-tools-dev%[email protected]> >>> > >>> >>> >> >> > > >>> >>> >> >> > > >>> >>> >> >> > > >>> >>> >> >> > > <rhino-tools-dev%[email protected]<rhino-tools-dev%[email protected]> >>> <rhino-tools-dev%[email protected]<rhino-tools-dev%[email protected]> >>> > >>> >>> >> >> > >>> >>> >> >> > > > > . >>> >>> >> >> > > > > For more options, visit this group at >>> >>> >> >> > > > >http://groups.google.com/group/rhino-tools-dev?hl=en. >>> >>> >> >> > >>> >>> >> >> > > -- >>> >>> >> >> > > You received this message because you are subscribed to the >>> >>> >> >> > > Google >>> >>> >> >> > > Groups >>> >>> >> >> > > "Rhino Tools Dev" group. >>> >>> >> >> > > To post to this group, send email to >>> >>> >> >> > > [email protected]. >>> >>> >> >> > > To unsubscribe from this group, send email to >>> >>> >> >> > > >>> >>> >> >> > > >>> >>> >> >> > > >>> >>> >> >> > > [email protected]<rhino-tools-dev%[email protected]> >>> <rhino-tools-dev%[email protected]<rhino-tools-dev%[email protected]> >>> > >>> >>> >> >> > > . >>> >>> >> >> > > For more options, visit this group at >>> >>> >> >> > >http://groups.google.com/group/rhino-tools-dev?hl=en. >>> >>> >> >> >>> >>> >> >> -- >>> >>> >> >> You received this message because you are subscribed to the >>> Google >>> >>> >> >> Groups >>> >>> >> >> "Rhino Tools Dev" group. >>> >>> >> >> To post to this group, send email to >>> >>> >> >> [email protected]. >>> >>> >> >> To unsubscribe from this group, send email to >>> >>> >> >> [email protected]<rhino-tools-dev%[email protected]> >>> . >>> >>> >> >> For more options, visit this group at >>> >>> >> >> http://groups.google.com/group/rhino-tools-dev?hl=en. >>> >>> >> >> >>> >>> >> > >>> >>> >> > -- >>> >>> >> > You received this message because you are subscribed to the >>> Google >>> >>> >> > Groups >>> >>> >> > "Rhino Tools Dev" group. >>> >>> >> > To post to this group, send email to >>> >>> >> > [email protected]. >>> >>> >> > To unsubscribe from this group, send email to >>> >>> >> > [email protected]<rhino-tools-dev%[email protected]> >>> . >>> >>> >> > For more options, visit this group at >>> >>> >> > http://groups.google.com/group/rhino-tools-dev?hl=en. >>> >>> >> > >>> >>> >> > -- >>> >>> >> > You received this message because you are subscribed to the >>> Google >>> >>> >> > Groups >>> >>> >> > "Rhino Tools Dev" group. >>> >>> >> > To post to this group, send email to >>> >>> >> > [email protected]. >>> >>> >> > To unsubscribe from this group, send email to >>> >>> >> > [email protected]<rhino-tools-dev%[email protected]> >>> . >>> >>> >> > For more options, visit this group at >>> >>> >> > http://groups.google.com/group/rhino-tools-dev?hl=en. >>> >>> >> > >>> >>> >> >>> >>> >> -- >>> >>> >> You received this message because you are subscribed to the Google >>> >>> >> Groups >>> >>> >> "Rhino Tools Dev" group. >>> >>> >> To post to this group, send email to >>> [email protected]. >>> >>> >> To unsubscribe from this group, send email to >>> >>> >> [email protected]<rhino-tools-dev%[email protected]> >>> . >>> >>> >> For more options, visit this group at >>> >>> >> http://groups.google.com/group/rhino-tools-dev?hl=en. >>> >>> >> >>> >>> > >>> >>> > -- >>> >>> > You received this message because you are subscribed to the Google >>> >>> > Groups >>> >>> > "Rhino Tools Dev" group. >>> >>> > To post to this group, send email to >>> [email protected]. >>> >>> > To unsubscribe from this group, send email to >>> >>> > [email protected]<rhino-tools-dev%[email protected]> >>> . >>> >>> > For more options, visit this group at >>> >>> > http://groups.google.com/group/rhino-tools-dev?hl=en. >>> >>> > >>> >>> >>> >>> -- >>> >>> You received this message because you are subscribed to the Google >>> Groups >>> >>> "Rhino Tools Dev" group. >>> >>> To post to this group, send email to >>> [email protected]. >>> >>> To unsubscribe from this group, send email to >>> >>> [email protected]<rhino-tools-dev%[email protected]> >>> . >>> >>> For more options, visit this group at >>> >>> http://groups.google.com/group/rhino-tools-dev?hl=en. >>> >>> >>> >> >>> >> -- >>> >> You received this message because you are subscribed to the Google >>> Groups >>> >> "Rhino Tools Dev" group. >>> >> To post to this group, send email to [email protected] >>> . >>> >> To unsubscribe from this group, send email to >>> >> [email protected]<rhino-tools-dev%[email protected]> >>> . >>> >> For more options, visit this group at >>> >> http://groups.google.com/group/rhino-tools-dev?hl=en. >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups >>> > "Rhino Tools Dev" group. >>> > To post to this group, send email to [email protected]. >>> > To unsubscribe from this group, send email to >>> > [email protected]<rhino-tools-dev%[email protected]> >>> . >>> > For more options, visit this group at >>> > http://groups.google.com/group/rhino-tools-dev?hl=en. >>> > >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Rhino Tools Dev" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<rhino-tools-dev%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/rhino-tools-dev?hl=en. >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Rhino Tools Dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<rhino-tools-dev%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/rhino-tools-dev?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rhino-tools-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
