[Anthill-pro] Thinking enterprise

[Curtis Yanko]

All,

Now that 3.2 is out  and presumably 3.3 is being developed, I want to 
revisit this now that I've have more experience with AH3 and a better 
understanding (or at least a more cogent way of expressing ) what I am 
trying to do.

I need to support 100's of "Products" where product is the enterprises 
view of an application. They don't much care that the application is 
actually made up of several sub-assemblies, to them it is just version 3.3 
of the Widget application. It is at this level of granularity that I'd 
like to present on the main Dashboard.

Each application is made up of one or more sub-assemblies (again, EARs, 
Static Files, DB Stuff...) which maps to what I would also call 
'deliverables' and the level of granularity that we want to build to. Each 
application would also have one or more 'components' (WARs, JARs, EJBs, 
Individual Static files, DB Scripts...) that are packaged in various ways 
to make our sub-assemblies. This is the level we want continuous 
integration to happen at (although push and pull scheduling obviously 
could impact sub-assemblies)

So on this Product (or Application) dashboard it would be great to have a 
matrix similar to the current status assignment one except the rows would 
be sub-assemblies and the columns would be statuses like success, failed, 
Dev, QA...  This would be a great high-level, Bill-of-Deliverables, view 
of the status of my product

An additional table for each component arranged the same way on this same 
dashboard (perhaps tabs would help with the presentation here) would make 
for a complete BOM view of the world.

IMHO, this is the kind of feature or add-on module that could help better 
separate your 'enterprise' product from something more suitable for the 
smaller shops.

For the record, I think that code re-use across the enterprise is a pipe 
dream. The reality is that we achieve that more as a software service than 
a code sharing thing. And when we do share code, it is a copy-paste 
exercise from one project to the next where the code is either tweaked or 
extended. More often a centralized group produces libraries that are 
passed around like log4j as binaries. Groups that really need to achieve 
it can solve it at the SVN layer more easily.

This is also exactly why I have been adamant from day one that if purchase 
AHP3 that we would get one of your guys in here to help us set it up 
'correctly' to avoid rookie mistakes. Unfortunately we have already begun 
very rudimentary pilot projects and are already having dialog along these 
lines about how we solve this for everyone in a scalable and supportable 
way.  For now we will stick with the more monolithic builds and play to 
your strengths. 

- Curtis Yanko
United Health Technologies
Mail Route: CT028-06SA
Internet email: curt_yanko at uhc.com
Office 860.702.9059
Cell 860.729.8171




Maciej Zawadzki <mbz at urbancode.com> 
Sent by: anthill-pro-bounces at caladin.urbancode.com
03/05/2007 01:58 PM
Please respond to
anthill-pro at caladin.urbancode.com


To
anthill-pro at caladin.urbancode.com
cc
anthill-pro at caladin.urbancode.com, 
anthill-pro-bounces at caladin.urbancode.com
Subject
Re: [Anthill-pro] Thinking enterprise






Curtis,

Sorry about the delayed response.

I think I understand exactly what you're looking for.  I think that
being able to create a tree of folders and being able to place projects
into folders would probably accomplish your goals.  There are other ways
of implementing something similar.  Frankly, this is on our road map for
3.3 and we have not given it too much thought yet.  Rather than trying
to rush something into 3.2, we'd like to make sure that we come up with
a good long term solution.  We can certainly make preview builds of 3.3
with this feature available to you.  In the mean time, I would not try
to correlate an AHP project with an assembly or team in your world.
Doing this would not set you up well for the solution that we'll have to
this problem in 3.3.

You can creates subdirs in the tags directory -- AHP should be able to
deal with that without a problem.

There is no way right now to send an email to everyone that is a
registered user in AHP.  Depending on how you're going to configure
Authentication, this may be easier done outside of AHP.  For example, if
all AHP users are in LDAP in a particular role, then it may be easier to
get them that way.  We'll add this as a feature request for 3.3 though.

Regards,

--Maciej
_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20070419/98783578/attachment.htm