[Pachy-Dev] Status report 2/2 -- continued...

Susan Baur susan at cdl.edu
Tue Feb 14 14:30:54 PST 2006


OK, the list pachy-users at lists.cdl.edu has been setup. It will be  
archived, but it may take a day or two for the archiving to be setup.  
If you'd like to subscribe, you can do so at https:// 
webmail.sonoma.edu/mailman/listinfo/pachy-users .

Some administrivia for those who are interested...
* We are not requiring approval of subscription requests, but are  
moderating all new member posts. Once a member has sent a non-spam  
message to the list an admin can unmoderate them.
* Replies to list messages go to the original poster by default. You  
will need to do reply-all to reply to the list (Just like this list.)
* Currently, messages are limited to 40K in size, so most attachments  
will not be accepted.

Let me know if you have any questions,

Susan

On Feb 14, 2006, at 1:28 PM, Joshua Archer wrote:

> Awesome, can you get that set up for us, Susan?
>
> Josh
>
> On Feb 14, 2006, at 1:13 PM, Susan Baur wrote:
>
>> Hi,
>>
>> I think the CDL could host the pachy-users list for now. That way  
>> the domains for the lists would remain the same. Also, if we limit  
>> maximum message size and make some other smart administrative  
>> choices, it would probably remain viable here at least for a  
>> couple of years if not longer.
>>
>> Susan
>>
>> --
>> Susan Baur
>> System Administrator
>> Center for Distributed Learning
>> 707-664-4408
>> susan at cdl.edu
>>
>>
>>
>> On Feb 14, 2006, at 10:54 AM, Joshua Archer wrote:
>>
>>> To start, I really think we need to open up a public mailing list  
>>> for pachyderm users. it should be called 'pachyderm-users' I  
>>> think (seems obvious enough).
>>>
>>> I think the CDL is currently hosting pachy-dev, but I am not sure  
>>> who is the appropriate host for a potentially high traffic  
>>> mailing list such as pachyderm-users. Any ideas?
>>>
>>> Josh
>>>
>>> On Feb 14, 2006, at 7:06 AM, Thomas Hapgood wrote:
>>>
>>>> We've talked about some type of Pachyderm community and now that
>>>> we have 400 users perhaps it should become a reality? What system/
>>>> software would we use for this? In terms of the gallery, I think in
>>>> several months it will start to fill up -- it's perhaps a bit  
>>>> early. I'll be
>>>> posting mine as soon as I can.
>>>>
>>>> tom hapgood
>>>> u. arkansas
>>>> interactive design
>>>> I thought I would pass this to the list for comment or input...
>>>>
>>>> Begin forwarded message:
>>>>
>>>>> From: Elisabeth Anne Leonard <anne at firstedit.com>
>>>>> Date: February 9, 2006 3:40:27 PM PST
>>>>> To: joshua at cdl.edu
>>>>> Cc: Rachel Smith <rachel at nmc.org>, Larry Johnson <johnson at nmc.org>
>>>>> Subject: Re: [Pachy-Dev] Status report 2/2 -- continued...
>>>>>
>>>>> fine with me!
>>>>> A.
>>>>>
>>>>> Joshua Archer wrote:
>>>>>> Awesome suggestions, Anne. Can we send this email to the pachy- 
>>>>>> dev list to get their input? I would love to see an 'advice'  
>>>>>> column, as well as promoting the use of the gallery.
>>>>>>> Hey y'all-- Should we consider having an "advice" column,  
>>>>>>> where users can submit their questions, and the questions and  
>>>>>>> answers are posted on-line? This could develop into an FAQ  
>>>>>>> eventually, as we get FAQs, but it might add some liveliness  
>>>>>>> to the website/blog. Also the gallery seems to have died on  
>>>>>>> the vine, maybe we should ask for sample screens and not  
>>>>>>> entire presentations?? Or send out the call again? I intend  
>>>>>>> to make mine public when it's completed. Anne Joshua Archer  
>>>>>>> wrote:
>>>>>>>> Part Two:
>>>>>>>> II. External Communication: In a certain sense, there is no  
>>>>>>>> line between internal communications and external  
>>>>>>>> communications for open source projects, as everything is  
>>>>>>>> open to the public and available for viewing/participation.  
>>>>>>>> However, there are different circles of involvement, and  
>>>>>>>> there are some basic communications in which the general  
>>>>>>>> user public will be interested, that are less detailed and  
>>>>>>>> less technical than the traffic on the dev list. The first  
>>>>>>>> thing we should look at critically is our website, and make  
>>>>>>>> sure it has all the things we're going to need for open  
>>>>>>>> source communication. We need to have our OS license  
>>>>>>>> available and prominently listed. We need to have links to  
>>>>>>>> our source, either the repository or downloadable tarballs  
>>>>>>>> at the very least. We need to have our documentation  
>>>>>>>> available, and instructions on joining the mailing lists,  
>>>>>>>> the development team, how to submit patches, etc. This is a  
>>>>>>>> process that will take some time and some attention. We also  
>>>>>>>> should be making better use of our Pachyblog, or we should  
>>>>>>>> move it to a section of our website (and at the very least,  
>>>>>>>> link to it from the main page). The traffic there has died  
>>>>>>>> to a trickle, and we need to be better about updating our  
>>>>>>>> public about the status of the project. I'm as guilty of  
>>>>>>>> this as anyone else. From the outside, we might appear like  
>>>>>>>> a dead or dying project. Let's breathe life back into the  
>>>>>>>> public facing. Again, we need to have the archives of our  
>>>>>>>> mailing lists readily available and prominent on the  
>>>>>>>> website, and I think we should also create one more mailing  
>>>>>>>> list right away, pachy-users@, so that we can funnel user- 
>>>>>>>> related questions and comments to that list. We should look  
>>>>>>>> into the establishment of a knowledge base, taking the form  
>>>>>>>> of a FAQ or a WIKI or something along those lines, so that  
>>>>>>>> we can capture the important information from the mailing  
>>>>>>>> lists and our experience as a project, and allow others to  
>>>>>>>> benefit from the process.  Also, a common occurrence in open  
>>>>>>>> source projects currently is to have an IRC channel always  
>>>>>>>> open for users/developers/etc. of the project. I'm going to  
>>>>>>>> look into getting this set up for pachyderm.
>>>>
>>>> ---------------------------------------------------
>>>> Joshua Archer
>>>> Software Engineer
>>>> CSU - Center for Distributed Learning
>>>> Phone: 707.664.2085
>>>> Fax:      707.664.4350
>>>>
>>>> _______________________________________________
>>>> Pachy-Dev mailing list
>>>> Pachy-Dev at lists.cdl.edu
>>>> https://webmail.sonoma.edu/mailman/listinfo/pachy-dev
>>>
>>> ---------------------------------------------------
>>> Joshua Archer
>>> Software Engineer
>>> CSU - Center for Distributed Learning
>>> Phone: 707.664.2085
>>> Fax:      707.664.4350
>>>
>>> _______________________________________________
>>> Pachy-Dev mailing list
>>> Pachy-Dev at lists.cdl.edu
>>> https://webmail.sonoma.edu/mailman/listinfo/pachy-dev
>>
>>
>> _______________________________________________
>> Pachy-Dev mailing list
>> Pachy-Dev at lists.cdl.edu
>> https://webmail.sonoma.edu/mailman/listinfo/pachy-dev
>
> ---------------------------------------------------
> Joshua Archer
> Software Engineer
> CSU - Center for Distributed Learning
> Phone: 707.664.2085
> Fax:      707.664.4350
>




More information about the Pachy-Dev mailing list