[sakai2-tcc] Contrib projects: reaching out to EDIA

[Jean-Francois Leveque]

Great move!

Indies don't have to be in the main svn or be officially approved.

You can do independent releases in contrib, even if you're doing it with 
the official rules.

Cheers,

J-F

Anthony Whyte a écrit :
> Just a head's up, but in regards to EDIA in particular,  I just sent 
> them a longish email outlining how they can upgrade their poms in order 
> to leverage the Maven release plugin (per their request).
> 
> I will provide them support as needed and starting on Friday begin to 
> crank out documentation on the mechanics of how to convert a project to 
> an indie.
> 
> Cheers,
> 
> Anth
> 
>  
> 
> On Jul 20, 2010, at 9:00 AM, Noah Botimer wrote:
> 
>> I would say, sure, play a buddy role if it's not filled... why not?
>>
>> But I do think that's what the Product Manager and Product Council are 
>> supposed to provide to the community -- a clear presence and process. 
>> Outreach and assistance for project teams in meeting community 
>> guidelines are, I think, intrinsic, explicit parts of those roles as 
>> defined.
>>
>> Maybe there is some room for a helping hand in that work, or maybe 
>> folks are just not aware that people still feel less informed or 
>> intimidated. I'm interested in systemic improvements in terms of 
>> discoverable, simple documentation and known, reachable presence. So, 
>> I'd rather see it get fixed than helped limp along if it's not set up 
>> right.
>>
>> As always, I think we have many people who are energized by workgroup 
>> membership and inspired to go beyond what the corpus of that group 
>> might see as its charge. This is a wonderful side effect and I 
>> encourage all the outreach we can muster, though I would also 
>> encourage it to happen in concert with other initiatives to be most 
>> effective.
>>
>> Thanks,
>> -Noah
>>
>> On Jul 20, 2010, at 8:32 AM, Berg, Alan wrote:
>>
>>> Hi,
>>>
>>> >The impractical, rhetorical response is: what's wrong such that a 
>>> group that makes a tool that fills a >gap doesn't know how or is 
>>> unwilling to advertise or advocate for said tool in a way that 
>>> catches >community attention? 
>>>
>>> It is not clear to me if the perceived barrier is too high for 
>>> smaller groups to be motivated to go through the process.  Can the 
>>> TCC play a buddy role?
>>>
>>> Alan B
>>>
>>> Alan Berg
>>> QA Director - The Sakai Foundation
>>>
>>> Senior Developer / Quality Assurance
>>> Group Education and Research Services
>>> Central Computer Services
>>> University of Amsterdam
>>>
>>> http://home.uva.nl/a.m.berg
>>> ------------------------------------------------------------------------
>>> *From:* Noah Botimer [botimer at umich.edu]
>>> *Sent:* 20 July 2010 14:13
>>> *To:* Berg, Alan
>>> *Cc:* sakai2-tcc at collab.sakaiproject.org 
>>> <mailto:sakai2-tcc at collab.sakaiproject.org>
>>> *Subject:* Re: [sakai2-tcc] Contrib tool to Sakai Enterprise core in 2.x
>>>
>>> An interesting and practical question.
>>>
>>> The impractical, rhetorical response is: what's wrong such that a 
>>> group that makes a tool that fills a gap doesn't know how or is 
>>> unwilling to advertise or advocate for said tool in a way that 
>>> catches community attention? Is this a problem worth solving if the 
>>> tool makers are disinterested?
>>>
>>> Regardless of the answers, there is a known set of documentation and 
>>> an outlined (albeit evolving) process for inclusion in the Sakai 
>>> release. Reaching out to a project team to show them that process and 
>>> how others have participated seems quite reasonable.
>>>
>>> I might first point to the "2.7 Exercise" and the range of projects 
>>> "formally considered" and see if EDIA might be interested in 
>>> participating in such a process.
>>>
>>> http://confluence.sakaiproject.org/display/MGT/2.7+Exercise
>>> http://confluence.sakaiproject.org/display/MGT/Development+Efforts+formally+considered
>>>
>>> Thanks,
>>> -Noah
>>>
>>> On Jul 20, 2010, at 7:48 AM, Berg, Alan wrote:
>>>
>>>> Hi Noah,
>>>>
>>>> I see improvement via a contrib tool. It may even ease issues for 
>>>> hybrid mode if looked at for Sakai 3.  Do we wait for the tool 
>>>> provider to come to us, which they will not or do we consider the 
>>>> technical merits and reach out if worth the effort. 
>>>>
>>>> Alan B
>>>>
>>>> Alan Berg
>>>> QA Director - The Sakai Foundation
>>>>
>>>> Senior Developer / Quality Assurance
>>>> Group Education and Research Services
>>>> Central Computer Services
>>>> University of Amsterdam
>>>>
>>>> http://home.uva.nl/a.m.berg
>>>> ------------------------------------------------------------------------
>>>> *From:* Noah Botimer [botimer at umich.edu]
>>>> *Sent:* 20 July 2010 13:37
>>>> *To:* Berg, Alan
>>>> *Cc:* sakai2-tcc at collab.sakaiproject.org 
>>>> <mailto:sakai2-tcc at collab.sakaiproject.org>
>>>> *Subject:* Re: [sakai2-tcc] Contrib tool to Sakai Enterprise core in 2.x
>>>>
>>>> My personal opinion is that there is an established contact channel 
>>>> for people interested in becoming part of the release. This is some 
>>>> combination of the Product Manager and Product Council.
>>>>
>>>> I think we should probably stick to our technical charge for now. 
>>>> Certainly, as community members, I think we should feel free to 
>>>> provide contacts and information to project teams, but I don't 
>>>> really see outreach as something to spend much of this group's time 
>>>> on for now.
>>>>
>>>> I'm happy for others to disagree, but I do see a measurable workload 
>>>> even on the finest grained definition of scope.
>>>>
>>>> Thanks,
>>>> -Noah
>>>>
>>>> On Jul 20, 2010, at 5:40 AM, Berg, Alan wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I was wondering if some tool makers in Sakai 2.x contrib are being 
>>>>> put off from getting their tools into Enterprise Sakai because we 
>>>>> may be putting  barriers in their way. I like the talk about the 
>>>>> application shop this will eliminate my concerns to some degree. 
>>>>> However, taking as an example the work by EDIA 
>>>>> (http://www.edia.nl/), I find the Knowledge base tool interesting 
>>>>> as a replacement for help http://sakaitools.edia.nl 
>>>>> <http://sakaitools.edia.nl/>. Does the TCC intend to look and reach 
>>>>> out to these tool makers and if so is EDIA a possible candidate for 
>>>>> communication.
>>>>>
>>>>> Alan B
>>>>>
>>>>> Alan Berg
>>>>> QA Director - The Sakai Foundation
>>>>>
>>>>> Senior Developer / Quality Assurance
>>>>> Group Education and Research Services
>>>>> Central Computer Services
>>>>> University of Amsterdam
>>>>>
>>>>> http://home.uva.nl/a.m.berg