On Wednesday, November 21, 2012 4:21:48 PM UTC+1, Andy wrote:
I'm thinking about moving our little library to GitHub and was wondering if anyone had an opinion.1. Do you think I should?
I'm not using your lib, so I can't comment here. As a consequence, do not give much weight to my comments below.
2. If you were going to contribute a feature or bugfix, would you be more likely to do so on GitHub?
This applies to any project: if you're not using a good code-review tool (Gerrit or Rietveld –e.g. codereview.appspot.com, Rietveld works best with Git and the git-cl script from repo-tools though–, there are probably others; I don't consider ReviewBoard a good tool, though it's still better than nothing), then yes, definitely: Pull Requests *are* a good code-review tool.
3. Do you think I should break it into a bunch of small projects or keep it in one jar? Most of the widgets are completely independent from each other.
We're about to break gwt-user into smaller JARs, but it'll still be one big repo (because we'll release all those JARs as a whole). We're still discussing the level of granularity though.
From the widgets/features advertized on your home page, I think I'd keep it as a single project and a single JAR. Maybe the AutoSizingTextArea could be split apart, because of its dependency on gwt-query; that doesn't mean it should be in a distinct repo though; depends what you release policy is.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/MaB6pkqeIPIJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment