On Sat, Jul 02, 2011 at 11:03:05AM -0400, Perry Myers wrote:
We've set up a bugzilla project for matahari on bugzilla.redhat.com site under the 'Community Classification'.
What about using github "issues" they are nice and lightweight. And the project is then hosted in one place.
The plan is to use this for tracking distro independent bugs as well as project features, etc.
Fedora bugzilla would then only be used for Fedora specific bugs, and we can easily mirror between Red Hat RHEL bugzilla, Fedora and the project.
What we need to do is define what 'components' we want to create under the Matahari project. In other places (Fedora, RHEL) a component maps to an SRPM, so from that perspective we'd only have two components in the matahari project: matahari and mingw32-matahari
Why? matahari is not exaclty a big project, isn't this just making more work when managing bugs?
But this seems not quite so useful
For upstream projects (see the Corosync Cluster Engine for example), the components of a project are broken down into functional areas rather than SRPM/RPMs.
Given that packaging is inherently a distro specific thing, I think it makes sense to map to functional areas. So the question is, what functional areas do we want to create as components for our project?
core libraries host agent net agent services agent config agent (well, after we decide on the naming here) dbus transport qmf transport
Thoughts?
Perry _______________________________________________ Matahari mailing list Matahari@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/matahari