ok I will get the repo setup at /var/erlware/repo unless someone has a better idea. Should be ready by eod.
El oct 28, 2010, a las 9:38 p.m., Martin Logan escribió: > ok, I have the portius_no_web release all setup. When ever the lightty stuff > is in place I can configure it and run it on the new machine. > > On Thu, Oct 28, 2010 at 1:48 PM, Jordan Wilberding <[email protected]> > wrote: > And so it begins. Our conversations drifted and jumped around a bit, > hopefully these notes make sense. > > --- > > *Martin* will look into getting our own privately hosted machine from Andy > Goodwin. It will be fully supported. Hopefully we can have Ubuntu on it. > > *Eric* will setup lighttpd once we get the new box. > > *Martin* will build a portius without the web frontend dependency once Eric > is done. > -- > > Martin brought up 4 primary standards we want to keep in mind > > 1. Coding guideline > This won't be anything to extensive. Just write good Erlang code. *Martin* > will take care of this. > > 2.Document public api > All public facing calls should be extensively documented. Input type and all > return types should be included > > 3. Spec everything > This goes along with documentation. Make sure you spec everything. *Eric* is > going to send out a writeup on this in a day or 2. > > 4. Vsn and deprecation > We want to create a clear contract with our end users on how deprecations > will be taken care of, including all guarantees we give the user. > > -- > > What should repo.erlware.org look like? > > Right now the debatable consensus is to have 2 primary repos. One is > moderated by us, the other is a universal one where everyone can write to it. > We are still deciding on this. > > We also need to consider the source vs binary package implications. > > We also want to be able to have people easily integrate with erlware from > wherever they host their code. For example, if someone has their code on > github, they should be able to setup a push notice that notifies us of a new > release. We then kick off an automated process that forks the code, builds > the app, and releases it. > > We have decided to use couchdb primarily over webdav. We are going to try to > keep the same REST interface, so webdav could still technically work. This is > assigned to *Tristan* > > We also have basically separated the package thing into 2 areas. > > 1. Managing. Where do they shit, how to upload, etc. *Tristan* is going to > take a stab at this > 2. Packages. Or as Eric likes to say "the bits and pieces themselves". > *Martin* was tentatively assigned this while off the phone. You're welcome. > > -- > > Finally, *all* of us are going to look at existing package managers to see > how adaptable they are to what we need. We are hoping to avoid solving the > same problems that everyone else already has. > > -- > > Assignment Summary: > > Eric: > Lighttpd > Spec doc > > Martin: > Get new server provisioned > Portius minus web > Code standards doc > Packages > > Tristan: > Couchdb otp'd > Managing portion of package stuff > > Me: > These notes > Integrate/transition slicehost/erlang.com with new erlang.org > > All: > Review current package managers > > > Thanks! > Jordan Wilberding > > -- > You received this message because you are subscribed to the Google Groups > "erlware-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/erlware-dev?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "erlware-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/erlware-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "erlware-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/erlware-dev?hl=en.
