Tatami future and licensing?

16 views
Skip to first unread message

mpickell

unread,
Apr 23, 2012, 11:31:11 AM4/23/12
to tatami
Can anyone comment on the status of Tatami? I know it is un-
maintained for quite some time, but I would like to use it and would
be happy to contribute back any changes/fixes/upgrades I make. Is
anyone associated with this project still around? Is it possible to
get access to update it or fork it?

Also, I see that licensing was opened up to APL and BSD as of v1.3,
but all of the header files still say LGPL as of v1.4? I guess it is
ok to just remove those headers and put in a header stating the
license I choose to use?

Ronan Dunklau

unread,
Apr 23, 2012, 11:56:54 AM4/23/12
to tat...@googlegroups.com, mpickell
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello.

I'm no longer involved with the project, but I remember the license
switch. It was done so that people more familiar with the APL could be
involved with the project.

As I'm not the copyright holder for the project, I unfortunately
cannot give you any definitive answer.

However, as with any open source project, you are free to fork it,
especially if it is no longer maintained.

I hope you will find answers to your questions from other people in
this list.

Best regards,

- --
Ronan Dunklau
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBAgAGBQJPlXu+AAoJECTYLCgFy323VK8H/iqvANR9xe7RozrGZ2dqStGu
KoZyFETyQCNj4eLUpbz/2Y7JWEQgXGMtUcXg0DN1cfhZMvxJmoEnmRrShxS7SuZ4
3BjXMkcvbGWTxuM0PrnTGFeyBW9wsEG4Hz2Yvk9mzuzIt4t7CMjzGPYM9LvdZNk+
LeVl6G1wCKfeDcOtDVMVNLhAaMIUXVwUCzvvN/vq8tUoqxZUl7kabJADTPusCA+K
yhXhgSZYX8jNS0ieJg7A1LikZ6SFFNLHnrVkuQM8G6JKdUracpwbHtJN4YglGBhN
lXxyD6c920E8joeWXNiNFCkMA+yKmJ6AqGOhxhUhLaxiSe8zfwFBHXtFRd2p6sE=
=lhOm
-----END PGP SIGNATURE-----

mpickell

unread,
Apr 23, 2012, 12:30:17 PM4/23/12
to tatami
Thanks for your response!

Do you have any recollection of why the license would have been
changed without any of the headers being updated?

Also, any idea from your history of why the project seemed to just
stop when there appeared to be a roadmap, etc?

Vianney Grassaud

unread,
Apr 24, 2012, 3:54:18 AM4/24/12
to tat...@googlegroups.com
Hello, 

Tatami is an Open Source project, 
I think we forget to update the headers in fact. You can choose the licence that you want. 

The project is not really stop. But we have no time to work on it correctly. 
But if you want to work on it, you can do it. 
The roadmap should be updated in order to take account the new GWT 2.0 features and last Dojo version. 
 
I can had you as a commiter member of Tatami if you want. You can also fork it, if you prefer. 

Thx for your interest in Tatami
Vianney 


--
You received this message because you are subscribed to the Google Groups "tatami" group.
To post to this group, send email to tat...@googlegroups.com.
To unsubscribe from this group, send email to tatami+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tatami?hl=en.




--
Guitare sans conscience n'est que ruine de l'âme...

La musique vaut toutes les philosophies du monde (Beethoven)

mpickell

unread,
Jun 5, 2012, 9:16:12 AM6/5/12
to tatami
Could you make me a member with commit privileges?

I am working on changing the header, and will post it here when i have
it ready for review. I'm using jQuery's header format as an example,
because it is very simple. For additional information I am adding a
link back to the Tatami site, so I would like to update the page to
point to the 3 different licenses, as well as update the license
section to state that any of those 3 are available.

Thanks!

mpickell

unread,
Jun 5, 2012, 9:17:11 AM6/5/12
to tatami
Also, one more thing. Do have any additional documentation on getting
the tests to run? Any setup information?

On Apr 24, 3:54 am, Vianney Grassaud <vgrass...@gmail.com> wrote:

Vianney Grassaud

unread,
Jun 13, 2012, 12:49:35 AM6/13/12
to tat...@googlegroups.com
hi, i added you as a commiter for tatami.

i think we should change a lot of things in tatami and we should use maven to build our release.
there is no documentation about test but just the test themselves. You can find them in the trunk (tests and testutil).

cheers,

Vianney
Reply all
Reply to author
Forward
0 new messages