On Jan 2, 2012, at 2:02 AM, Kitson Kelly wrote:
Source Code - I am more familiar with SVN and need to learn about GitHub, because it is likely the "way forward".
Yes, I would think this should be a prerequisite for being a dojo contributor. And unfortunately, Git is a royal PITA for those of us who are not unix heads or repo administrators. Fortunately, GitHub released a GIT GUI which works quite well on a Mac. (and only Mac as near as I can tell)
Packaging - Need to learn more about CPM and how I get my package on the package website. Problem is I have installed CPM multiple times on my Mac, following the "simple instructions" and it fails with an error, and I can't be asked to try to figure out how I file a bug for it, because it is already something that is "off on its own".
Kris and Bryan added a fix so you can install that in a custom folder that is not usr/local which gives the Mac permissions problems. I think you still need to modify your .bash_profie yourself though. And it looks like it doesn't work with Node.js, and you have to leave it defaulting to Java for now.

But you make a good point. CPM looks like the doorway to Dojo 2.0 - and it's currently bottlenecked by how much bandwidth Kris has to maintain it.
Bug Tracking - This is my biggest "barrier" to entry at the moment. I am comfortable with a few, but currently, there is nothing I can "plug into" that will "work" with the rest of the community.
If you mean for your own widgets - I would think GitHub's Issue Tracker would work. IMHO
Test Automation - I need to learn more about DOH. That is my biggest "challenge" for prepping my code, in my opinion for Primetime. I would hate for the community to devolve into a bunch of hackers who don't worry about testing. While it is a pain, it should be a "requirement".
I've never used testing in my DojoX projects and I don't think this makes the code less good. The problem with not using testing is it's harder on the committer, because you tend to not know your code was broken by low level changes until the last minute, or even after the fact, so you usual scramble to fix everything before a release. So I don't see this as a requirement. Plus, the idea of extensions is that versioning would be relaxed. Just because Dojo releases 2.5, it doesn't mean your extension automatically works with 2.5 on that date. Ideally it would, but your lack of update would not hold up the release.
Documentation - I have contributed quite a few small chunks to the Dojo documentation and have my head "wrapped around" the markup, but there is no clear way to "plug it in" to the rest of community. As far as source code documentation, I know there has been a lot of debate about source code API documentation is broken rather extensively. Don't know what to do about that.
On GitHub, if a page has a .md markdown extension, it will show as an HTML file. Now, if you can do that for more than one file, or if it always has to be "readme" I'm not sure.
Coding Style - I think I have done it the Dojo way, but I am more then willing to take input and feedback from anyone (as well as code contributions).
That would be easier moving forward because your code would live in a public repo and you would get free advice and style suggestions.
So it is even more important for me to contribute my stuff in a way that it has an opportunity of surviving without me, if it useful to others on its own merits.
That's a worthy goal, but hard to do. Most DojoX projects are maintained by one person. And many are orphans, which is the whole point of the extension plan.

Mike Wilcox

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.dojotoolkit.org/pipermail/dojo-contributors/attachments/20120102/befddb35/attachment-0001.htm

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 17 of 39 | next ›
Discussion Overview
groupdojo-contributors @
postedDec 22, '11 at 9:14p
activeJan 4, '12 at 2:37p



site design / logo © 2021 Grokbase