Am 28.03.2012 um 08:06 schrieb ISHIMOTO Ken: > It's not only time, it is really difficult for not Core User to make changes. > > If you not a Core Contributor, > > * nobody cares about your code, > * if you say there is a Bug, nobody believes you > ... > > I also work 365/year on wonder and have many Frameworks now. Also it is funny > to see that Bugs that I fixed, > someone other fixes the some Problem months later. Find and fix the same > Bugs, sometimes very time consuming. > > But really no idea how that can every be fixed. > > I am really try now with Pascal first Baby-steps for committing some javadoc, > but some old Classes are so bad formatted, > it is also Time to go through and make some reformatting in one "reformatting > only Commit".
Perhaps now it is the time to define a mandatory Wonder code formatter all commits have to use. I think that would make it easier for many committers to send patches without worrying about formatting – and it would improve the code readability/quality. > > But nobody will do that because some other Members maybe go angry about that. > > It is a Community on one side, on the other site it is very closed to a few > People only. > > > On 2012/03/28, at 6:26, Paul Hoadley wrote: > >> Hi, >> >> On 28/03/2012, at 11:55 AM, Ted Archibald wrote: >> >>> There's also a 4th reason: People like me who don't know git/github, and >>> don't know how to integrate it into my workflow. I'd like to contribute >>> more, but I need to spend a day or two figuring out how to get from here to >>> there without breaking my current workflow much. >> >> IMHO, this is a huge deal (in that it's essentially a technical problem, not >> a political or motivational issue, and something that is so easily fixed). >> Ted―what would it take to get you up and running? Is it just time? Is the >> wiki documentation adequate, or is there something you're unsure about? >> >>> For instance I currently have laying around a basic twitter framework, >>> httpclient framework, xgrid framework, crowdflower framework etc. etc. just >>> gathering dust. I also have random subclasses since it's quicker for me to >>> subclass and fix a bug in wonder instead of working with wonder directly. >>> >>> On my list of todo's I need to rewatch your contributing to wonder video >>> then learn up on Github and Tailor so I could post to github from my svn >>> commits. >> >> In the meantime, I am more than happy to get anything you have into Wonder. >> Send me some of your random subclasses, like the AjaxFlickrBatchNavigation >> fix. Same goes for anyone else: I volunteer here and now to help anyone get >> their stuff into Wonder where the problem is purely unfamiliarity with >> Git/GitHub. >> >> >> -- >> Paul. >> >> http://logicsquad.net/ >> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/ken%40ksroom.com >> >> This email sent to k...@ksroom.com > > Thank you > > Ken Ishimoto > > -------------------------------------------------------- > K's ROOM > -------------------------------------------------------- > [E-Mail] <k...@ksroom.com> > [iChat:] <ibase_...@mac.com> > [HP] http://www.ksroom.com/ > _____________________________________________________________________ > This e-mail has not been scanned for viruses because it was written on an Mac, > and there are NO Viruses on an Apple Computer. > For further information visit http://www.apple.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
