Kieran,

It is not because I work to much or anything else. I really love and enjoy work 
and that's fine for me.

I was trying to get together for two reasons.

1. To Contribute

2. To make my life easier, because if there is only one Version than I don't 
have to maintenance always 2 big frameworks.


Ken

On 2012/03/30, at 14:42, Kieran Kelleher wrote:

> Ken,
> 
> One suggestion: just host your Wodka project on github so that the source is 
> available to all...
> 
> "WODka: A Wonder variant built for the Japanese market"
> 
> .... and if people want to port elements back,they can cherry-pick stuff they 
> want. again this puts responsibilities for work on people with *needs and 
> wants*. Why should you have to worry about it. If you publish and manage the 
> project you have derived from Wonder on a public open-source platform such as 
> github, you have done your part. And that is totally understandable since, as 
> you said, it has diverged so much that it is no longer feasible to merge, and 
> besides you are over-worked.
> 
> So, can you move Wodka to github to its own account and use github for your 
> continued development and collaboration with the 8 or so Japanese companies?
> 
> Regards, Kieran
> 
> 
> 
> On Mar 30, 2012, at 4:39 AM, ISHIMOTO Ken <[email protected]> wrote:
> 
>> There are two kind of new Contributor
>> 
>> 1. Real wonder or plain WebObjects User, the make some changes and it's done.
>> No way that is no big problem and I hope a lot of People will contribute in 
>> the Future.
>> And of course make a Fork, make chances, push done... HAPPY
>> 
>> But I am not one of this group. That's my Problem.
>> ---------------------------------------------------------------------------------------------------
>> 
>> 2. The good question what is my Problem?
>> 
>> To make it a bit easier, here is a picture.
>> 
>> <WodkaFlow.png>
>> 
>> We are a Group of about 8 Companies who use "wodka" Framework in a lot of 
>> Projects. Sometimes it is a small
>> WebSite, sometimes it is a Million Project in-house. We are usually testing 
>> most Software very hard, that is way in
>> Japan. It has to work. Most Bug-fixes we do inside our Framework, but I had 
>> only the chance to contribute a few fixes to wonder yet.
>> 
>> Because 7 Companies here are speaking only Japanese, it is only me you can 
>> see on the List.
>> We make a lot translations and javadoc into japanese.
>> 
>> 3 years ago we decide to start use wonder, It was a hard transition, but we 
>> moved class by class to our framework. Most important classes
>> are already full javadoc translated. Of course we don't like warning too. We 
>> fix warning, and reformat most source for better readability.
>> The formatting isn't a big deal, I can provide a sample what we did if you 
>> like.
>> 
>> On top of Wonder there are sitting a lot of our Classes that we use, like 
>> Double Byte Conversation a new Hyperlink class and a lot more.
>> 
>> On top of all are about 10 Frameworks. 
>> 
>> My workflow :
>> 
>> I am getting change, fixes and requests to create frameworks from the 
>> Companies. The Frameworks grows every day. But the are all under heavy usage.
>> Once a week, I look into the new wonder Source changes, and every line will 
>> transfer to our Framework version. Line by Line.
>> That's also a reason why I know most changes and can support a lot of our 
>> companies. But it is also a reason to make my life hard, because I have to
>> work a lot. 100 hours/week mostly. That's also why I am not always on the 
>> List, because I have no time, and I have mostly no Question because we try 
>> to figure
>> everything out and that's good for learning new stuff. Off course we are not 
>> perfect.
>>  
>> Now I was talking to Pascal how we can maybe work more together. And I am 
>> thinking about it. But it is not done make a fork click click done.
>> It is more work, I am willing to help but it was only an idea. To move our 
>> Frameworks, we have to move the Wonder core changes at first and that one 
>> class after the next class.
>> Git will do nothing for us, because our Code is mostly nice formatted, and 
>> Git will show 100% changes^^
>> That is not a show-stopper because I do it every day. But it was only an 
>> idea. We did our Job now for about 10 years (Me 5 years) for WO on our own,
>> and we have no Problem to go without getting together. Because new blood and 
>> new ideas make a Community powerful that's why I try to get together.
>> But for our other Members here the don't really care because the don't speak 
>> english anyway.
>> 
>> Only to understand my Problem that it is not so easy as make a change to the 
>> CLASSPATH. It is depressive to see people speak about stuff the have no idea.
>> 
>> Ken Ishimoto
>> 
>> 
>> On 2012/03/29, at 21:03, Lachlan Deck wrote:
>> 
>>> It seems a core concept of smaller building blocks is being overlooked in 
>>> favour of the monolithic all-or-nothing-one-stop-shop.
>>> 
>>> Wonder, itself is a set of frameworks built ontop of other frameworks/jars. 
>>> There is no need for 'everything' to live inside Wonder.
>>> 
>>> <sarcasm>
>>> There's this neat little feature of java called a classpath that you could 
>>> 'extend' :)
>>> </sarcasm>
>>> 
>>> If you've got your own concentrated and reusable stuff that you want to 
>>> share, do it: make a framework/jar available, post each version to 
>>> WOCommunity's maven repo. Write your howto/docs on your project's github 
>>> page, make it known. Simple. If people like it they'll use it, fork it, 
>>> contribute back to it.
>>> 
>>> cheers,
>>> Lachlan Deck
>>> [email protected]
>>> 
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list      ([email protected])
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/ken%40ksroom.com
>>> 
>>> This email sent to [email protected]
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/kelleherk%40gmail.com
>> 
>> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to