<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Yes, Maven for example: http://maven.apache.org/index.html</span></div><div><span><br></span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Fred Moyer <fred@redhotpenguin.com><br> <b><span style="font-weight: bold;">To:</span></b> Jeffrey Thalhammer <jeff@imaginative-software.com> <br><b><span style="font-weight: bold;">Cc:</span></b> sfpug@sf.pm.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Friday, February 10, 2012 1:22
PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [sf-perl] Looking For Software Asset Management Tool Recommendations<br> </font> </div> <br>
> The fundamental question they want answered is:>> When a new version of a project is released, whom do I need to notify?<br>The ASF has developed a fairly robust structure and set of processes<br>for software development that may be worth examining to see if your<br>organization is facing similar problems. JIRA is used for issue<br>tracking on some projects, but like any piece of software there it has<br>shortcomings, breaks as much as any other software does, and gets<br>disparaged by the users on a daily basis.<br><br>I'd suggest reading through the Apache website, if nothing else than<br>to see how the organizational structure has evolved to manage several<br>hundred projects which power a good chunk of the web -<br>http://apache.org/<br><br>2012/2/10 Jeffrey Thalhammer <<a ymailto="mailto:jeff@imaginative-software.com" href="mailto:jeff@imaginative-software.com">jeff@imaginative-software.com</a>>:<br>> Hi everyone-<br>><br>>
My client is trying to get a grip on their software. It is a mid-sized<br>> organization and they have over 100 different home-grown software "projects"<br>> that all live in one Subversion repository. There are various<br>> interdependencies among the projects. For example project A may depend on a<br>> database provided by project B. Or project C may depend on a web service<br>> provided by project D. The fundamental question they want answered is:<br>><br>> When a new version of a project is released, whom do I need to notify?<br>><br>> So basically they need to track project owners and dependencies between<br>> projects. They have started building a home-grown solution to do this, but<br>> it is quickly spiraling out of control. I figure every large enterprise has<br>> this exact same problem, so there has to be some off-the-shelf solutions out<br>> there. I
believe the general term for this (and related things) is Software<br>> Asset Management. So my questions for all of you are:<br>><br>> Have you solved this kind of problem in your organization? How did you solve<br>> it? Did you use an off-the-shelf solution (either in part or in full)? If<br>> so, which one and would you recommend it?<br>><br>> -Jeff<br>><br>> _______________________________________________<br>> SanFrancisco-pm mailing list<br>> <a ymailto="mailto:SanFrancisco-pm@pm.org" href="mailto:SanFrancisco-pm@pm.org">SanFrancisco-pm@pm.org</a><br>> http://mail.pm.org/mailman/listinfo/sanfrancisco-pm<br>><br>_______________________________________________<br>SanFrancisco-pm mailing list<br><a ymailto="mailto:SanFrancisco-pm@pm.org" href="mailto:SanFrancisco-pm@pm.org">SanFrancisco-pm@pm.org</a><br><a href="http://mail.pm.org/mailman/listinfo/sanfrancisco-pm"
target="_blank">http://mail.pm.org/mailman/listinfo/sanfrancisco-pm</a><br><br><br> </div> </div> </blockquote></div> </div></body></html>