[sakai2-tcc] Project Keitai commits

[Aaron Zeckoski]

I'm sure for the CLE team maintained stuff it should be fine (IMO
anyway) though to be more formal you may want to ask the
cle-release-team at collab.sakaiproject.org for completeness (I don't
think that is necessary though).

That is the process that I and (most?) other CLE team members tend to
follow and even though it isn't exactly formalized, I think it results
in higher quality code and avoids stepping on toes.
-AZ


On Thu, Mar 14, 2013 at 7:16 AM, Steve Swinsburg
<steve.swinsburg at gmail.com> wrote:
> Thanks for the feedback Aaron.
> We will be working with the message centre team on this particular feature so that will be fine I am sure. And likewise for other projects with active teams.
>
> I was mainly talking about the core projects where there is no defined project team (and the only other one on the list is Dashboard and I've already contacted Jim)
>
> cheers,
> Steve
>
>
> On 14/03/2013, at 10:07 PM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>
>> My opinion is that projects with active project teams or leads (e.g.
>> message center) should just have a a patch attached and should be
>> assigned to them to review and commit. This is the practice that I
>> follow and I think it is respectful of the people who maintain that
>> code. It also give others a chance to apply this patch to older
>> versions if they want the functionality.
>>
>> -AZ
>>
>>
>> On Wed, Mar 13, 2013 at 10:33 PM, Steve Swinsburg
>> <steve.swinsburg at gmail.com> wrote:
>>> Hi all,
>>>
>>> Project Keitai is underway and very soon there will be some modules being
>>> completed for multiple projects. I will be reviewing all work completed to
>>> ensure it meets the specifications and is in line with what the Project
>>> Keitai committee has agreed upon, but in the interest of meeting the
>>> deadline for Phase 1, I hope no one minds these commits going directly in to
>>> the various projects? If you do, please contact me.
>>>
>>> Code will be added to its own area of each tool for the providers. Where a
>>> provider already exists, that one will be reviewed/enhanced if required, but
>>> no disruption to any tool/service or existing provider is expected.
>>>
>>> Parent task is here, currently a WIP as I add the details for each project.
>>> https://jira.sakaiproject.org/browse/SAK-23352
>>>
>>> regards,
>>> Steve
>>>
>>>
>>>
>>> _______________________________________________
>>> sakai2-tcc mailing list
>>> sakai2-tcc at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>>
>>
>>
>>
>> --
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile