I was thinking about the organization of the project and I think it would be better if it followed the pattern some other projects have established when they have a large plugin architecture. Rather than have a single project for all the patches, create a Ruby Patches organization, and a have a separate project for each patch. That way each patch can be versioned independently and all patches for each version of Ruby will be together. The project layout for each patch would be like:
README.md
1.9/
some-patch.diff
jruby/
some-patch.diff
This would make it much easier for people to work with the particular patch they are interested in and help support it.
Another benefit it that ruby-patches would then have it's own website under the organization url.
What do you think?
I was thinking about the organization of the project and I think it would be better if it followed the pattern some other projects have established when they have a large plugin architecture. Rather than have a single project for all the patches, create a Ruby Patches organization, and a have a separate project for each patch. That way each patch can be versioned independently and all patches for each version of Ruby will be together. The project layout for each patch would be like:
This would make it much easier for people to work with the particular patch they are interested in and help support it.
Another benefit it that ruby-patches would then have it's own website under the organization url.
What do you think?