Menu
▾
▴
ottoproject-devel — Otto Project Development
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(8) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <ben...@id...> - 2004-05-22 12:27:22
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: Bruno C. <br...@wh...> - 2003-05-02 19:57:52
|
TJ> Heh...forgot an important one: we'll need to setup an Otto TJ> network first. =) Ah yes, that would help. :-) I have some SPARCs I can get going this weekend. Does anyone have any preference on public vs. private IP addressing? b. -- /* Bruno Connelly, <br...@wh...> */ |
|
From: Bruno C. <br...@wh...> - 2003-05-02 19:55:46
|
TJ> For release policies, do we want the "release early, release TJ> often" approach, where we basicially release everything we have TJ> now (don't know how many would download it, or where we'd TJ> announce it [I just registered ottoproject on freshmeat.net]), TJ> or we could have semi-definite roadmaps for each release. I'm personally not a fan of the "new release every two weeks" approach, and would rather just have real release schedules. Just my opinion, of course. Speaking of where to announce, who would download, etc -- we probably should start thinking of some evangelistic outlets to get people clued into and interested in Otto. Publishing is one easy way to accomplish this, but we need at least one semi-solid release first, IMO. Maybe posting to some relevant lists would be helpful (not sure what those would be)... but maybe having at least an initial release first is a pre-requisite so people would have something to actually check out? I'm a quasi-regular on the mod_perl list (which actually has a decent amount of intelligent, clued regulars) which might be a decent place to gauge others interest in Otto. TJ> The things, as I see them, that would probably be required for a TJ> first release: TJ> - migration to Postgres and/or MySQL for the db backend stuff TJ> - writing of installer scripts and/or instructions (RPMs?) for TJ> installation TJ> - basic usage docs/User Guide/Tutorials TJ> - User ACLs TJ> - fully breaking the Agent registration step out of the TJ> Inventory module Yep, all of the above are important. There are quite a few things I'd like to do with regard to the registration/inventory separation pieces, but I'll wait until we have a bugzilla instance going again to get discussion started on that -- or do we want to try and use the sourceforge bug tracking system? The things I see as the most important for an initial release (in no particular order): migration away from Oracle (or support for an RDBMS in addition to Oracle), Inventory/registration separation and docs/guides/etc. RE: packaging, I think there's a lot to talk about there as well. I'm somewhat envisioning a make-maker (typical Perl style release, Makefile.PL, etc) and then some instructions for putting the other pieces together (how to get an Apache instance ready, libraries required, etc, etc). ...not sure what you guys think, if you'd rather try and take an autoconf route (would make sense if we eventually get some non-Perl pieces in the core distribution), etc, etc. TJ> Other infrastructure stuff we'll probably want/need: [...] Yes, we should get ottoproject.org. Who wants to register it? apogee (ns{1,2}.whack.org) could happily do DNS for it (and even more if necessary). b. -- /* Bruno Connelly, <br...@wh...> */ |
|
From: TJ S. <tj...@ca...> - 2003-05-02 19:34:07
|
bruno>I'll get the commit emails going later unless someone beats me to it.
Can you direct the commit emails to the ottoproject-cvs list? You may
need to tweak the Mailman settings to let the email through without
moderation...
TJ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
But let there be spaces in your togetherness.
-Kahlil Gibran
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
From: Bruno C. <br...@wh...> - 2003-05-02 19:24:31
|
FYI, the initial import is done. I did a few check outs and everything looks fine. I did include our original CVSROOT module, but they replaced it with a vanilla one (which is fine, but means we need to re-setup the commit e-mails). I'll get the commit emails going later unless someone beats me to it. b. ----- Forwarded message from "SourceForge.net" <no...@so...> ----- Envelope-to: br...@wh... To: no...@so... From: "SourceForge.net" <no...@so...> Subject: [ alexandria-Support Requests-731056 ] CVS import request: ottoproject Date: Fri, 02 May 2003 06:31:09 -0700 X-Spam-Status: No, hits=1.7 required=5.0 tests=SEARCH_ENGINE_PROMO version=2.53 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) Support Requests item #731056, was opened at 2003-05-01 18:59 Message generated for change (Comment added) made by burley You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200001&aid=731056&group_id=1 Category: Project CVS Services Group: Second Level Support >Status: Closed Priority: 3 Submitted By: Bruno Connelly (brucon) Assigned to: David Burley (burley) Summary: CVS import request: ottoproject Initial Comment: Hello, Could you please import an existing CVS root for the 'ottoproject' project at your earliest convenience? A tarball of the CVS root has been placed in the group directory here: /home/groups/o/ot/ottoproject/cvsroot.tar.gz Do let us know if there are any questions. Thanks! --bruno ---------------------------------------------------------------------- Comment By: David Burley (burley) Date: 2003-05-02 09:31 Message: Logged In: YES user_id=597273 Greetings, Per your request, the contents of the specified tarball or zip archive have been placed within your SourceForge.net project CVS repository. Should you require further assistance from the SourceForge.net team, please submit a new support request. Thank you, SourceForge.net support ---------------------------------------------------------------------- Comment By: David Burley (burley) Date: 2003-05-02 07:17 Message: Logged In: YES user_id=597273 Greetings, This canned response is used by the SourceForge.net team to convey information about how this Support Request will be handled. Please read the entirety of this comment before taking any further action; information enclosed in this comment will help you to ensure that you have an excellent support experience. The SourceForge.net team takes all reported issues seriously; we will work to provide you a complete, accurate, and timely response to your inquiry. Information about our support policies and procedures may be found at: https://sourceforge.net/docman/display_doc.php?docid=11230&group_id=1 ABOUT THIS ISSUE: Based on the initial review of this request, we have determined that this issue will be considered to have High Priority (this is signified by the summary line we use on this request, not by the Priority setting on this request). Issues within this category typically include requests for handling the import of content to a CVS repository (either from a tarball of an existing CVS repository, or from a source tarball). A description of this class of issues may be found at: https://sourceforge.net/docman/display_doc.php?docid=11230&group_id=1#issueclass_high TRIAGE PROCESS: The initial review of this issue has resulted in a member of the SourceForge.net staff determining who should process this issue, and a change in the Priority, Summary, Assignee, Group and Category settings for this request. We use these settings solely for grouping purposes; as the submitter, you SHOULD NOT change any of these settings. Since we use all of these settings to group issues for faster response, you should understand that changing any of these settings (particularly the listed Priority setting) will result in significant delays in the processing of your request. WHAT TO EXPECT: Issues of this nature will typically be reviewed again by the assigned member of the SourceForge.net team within 3 business days (the SourceForge.net team works at least Monday through Friday, 9am to 5pm Pacific, excepting holidays), though most issues of this nature are handled within 24 hours of submission. Within our next response, we will typically either perform the requested import of your CVS repository, or ask for clarification of this issue report. Please wait patiently for our next review of, and response to, this request. INQUIRING ABOUT THE STATUS OF THIS ISSUE: Should you have questions or concerns regarding the status of this issue, simply add a comment to this support request. All comments you post to this support request will be received by the SourceForge.net team member who has been assigned this issue. Please do not submit a second support request about this issue (add a comment to this request instead), and do not attempt to contact the assignee of this request via email; all additional information or comments about this request should be posted as a comment to this request. Thank you, SourceForge.net support ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200001&aid=731056&group_id=1 ----- End forwarded message ----- b. -- /* Bruno Connelly, <br...@wh...> */ |
|
From: TJ S. <tj...@ca...> - 2003-05-02 04:47:35
|
tj>The things, as I see them, that would probably be required for a first tj>release: Heh...forgot an important one: we'll need to setup an Otto network first. =) TJ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ We are ashamed of everything that is real about us; ashamed of ourselves, of our relatives, of our incomes, of our accents, of our opinions, of our experience, just as we are ashamed of our naked skins. -George Bernard Shaw ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
|
From: TJ S. <tj...@ca...> - 2003-05-02 04:04:10
|
Now that Otto is free (woohoo!), we'll want to draft up the stuff we think we need/want to have done before doing a release...and even to come up with a release policy. For release policies, do we want the "release early, release often" approach, where we basicially release everything we have now (don't know how many would download it, or where we'd announce it [I just registered ottoproject on freshmeat.net]), or we could have semi-definite roadmaps for each release. The things, as I see them, that would probably be required for a first release: - migration to Postgres and/or MySQL for the db backend stuff - writing of installer scripts and/or instructions (RPMs?) for installation - basic usage docs/User Guide/Tutorials - User ACLs - fully breaking the Agent registration step out of the Inventory module Other infrastructure stuff we'll probably want/need: - non-SF domain, e.g. ottoproject.org? That way, we could (initially) have ottoproject.org simply redirected to ottoproject.sourceforge.net. - website (what Otto is, goals, how it works, who we are, that whitepaper/high level stuff, etc) - bug database (do we want to use SF's bug tracker, or set up a Bugzilla instance on something like bugs.ottoproject.org) - CVS and releases: I think it'd be a good habit if, when we want to do a release, we create a branch from the main development trunk and release from there. It'll make maintenance of multiple releases (e.g. alpha/beta/RC/stable) easier. TJ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To believe in something, and not to live, is dishonest. -Mahatma Gandhi ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
|
From: Bruno C. <br...@wh...> - 2003-05-01 23:29:06
|
TJ> Just to be the first post on the list, and to send out the info TJ> bruno posted on #otto: [...] Wow, does mailman put enough list headers in there or what? :P ...also, is there anyway to configure mailman to set the 'Reply-to' header so we don't get multiple response copies? Or should we all just be smart enough to have procmail nuking dupes? b. -- /* Bruno Connelly, <br...@wh...> */ |
|
From: TJ S. <tj...@ca...> - 2003-05-01 23:24:23
|
Just to be the first post on the list, and to send out the info bruno posted on #otto: https://sourceforge.net/tracker/index.php?func=detail&aid=731056&group_id=1&atid=200001 TJ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There is no danger to a man, that knows What life and death is; there's not any law Exceeds his knowledge, neither is it lawful That he should stoop to any other law. He goes before them, and commands them all, That to himself is a law rational. -George Chapman ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
