question, is it ethical for us to look at a commercial project like Nexus staging and try to imitate its feature?
-Dan On Fri, Apr 2, 2010 at 1:15 PM, eshan sudharaka <[email protected]> wrote: > > i went through the Nexus tutorial and finally came up with the following > approach.This is very high level and i need help from u guys to fill the > missing part. > > * Assign a Temporory reposotory for a group.(eg : com.MyTempRep.example) > > * Only they are allowed to publish artifacts and the tempo rory repo is only > open to them untill deploye the all artifacts to be tested.(not > visible to > the common repo with have tesed modules) > > * once the temporory reposotory is closed it should me prevented from the > developers being updating and it should be opened to QA people to > testing(Same temporory repo will be used.only acces grants should be chaged > and assing the acces for the QA group) > > * once testing is done > if it success then merge the temp repo to the > common repo(where the tested modules are located) > > > > if it fails then manually removed from the repo. > > I dont understand how the audit log is linking with this project idea.could > u please explain it? > and also are we need to wary about the changes that are done in the > artifacts in temporary repo (by developers).I mean whether we should provide > a facility like svn diff ? > > eshan sudharaka > thank you > > > > > Deng Ching-2 wrote: >> >> I already filed the project ideas we've discussed in the ASF JIRA: >> >> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&query=Archiva+&summary=true&description=true&pid=12311010&status=1&customfield_12310260=gsoc >> >> -Deng >> >> On Wed, Mar 24, 2010 at 7:50 AM, Deng Ching <[email protected]> wrote: >> >>> I got a reply from the student who contacted me about GSoC and he said >>> he's >>> still interested :) His name is Eshan Sudharaka btw. >>> >>> Thanks, >>> Deng >>> >>> >>> On Tue, Mar 23, 2010 at 2:31 PM, Deng Ching <[email protected]> wrote: >>> >>>> Heh I think we hit send at the same time. I sent an email already to >>>> [email protected] for a request for the Archiva project to be >>>> added to the ASF Jira so we could file issues for the GSoC :) No reply >>>> from >>>> them yet though. >>>> >>>> -Deng >>>> >>>> >>>> On Tue, Mar 23, 2010 at 2:27 PM, Brett Porter <[email protected]> wrote: >>>> >>>>> I moved this over to the wiki and will mail it to >>>>> [email protected]. I only added a few since we don't have that >>>>> many mentors. >>>>> >>>>> Any further ideas / volunteers? >>>>> >>>>> I think we should add some more detail to the staging / promotion one. >>>>> Anyone have particular thoughts on it? >>>>> >>>>> - Brett >>>>> >>>>> On 17/03/2010, at 11:13 AM, Brett Porter wrote: >>>>> >>>>> > Hi, >>>>> > >>>>> > Do we want to propose any projects for Google Summer of Code for >>>>> Archiva? >>>>> > >>>>> > These are the sorts of ones I can think of: >>>>> > - MRM-976 - introduce a better event API >>>>> > - MRM-1209 - project tree view >>>>> > - MRM-980 - merging repositories >>>>> > - MRM-1021 - staging / promotion >>>>> > - atomic deployment (as discussed by Marc on here recently) >>>>> > - Propose your own / pick from from the backlog >>>>> > >>>>> > Thoughts / volunteers / priorities? >>>>> > >>>>> > - Brett >>>>> > >>>>> > -- >>>>> > Brett Porter >>>>> > [email protected] >>>>> > http://brettporter.wordpress.com/ >>>>> > >>>>> > >>>>> > >>>>> > >>>>> >>>>> -- >>>>> Brett Porter >>>>> [email protected] >>>>> http://brettporter.wordpress.com/ >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>> >> >> > > -- > View this message in context: > http://old.nabble.com/GSoC-projects--tp27926425p28122612.html > Sent from the archiva-dev mailing list archive at Nabble.com. > >
