Google Buzz
Hannes Boran
Two things:
* First, i just added Google Buzz as a data source. Patch here:
http://pastebin.com/raw.php?i=2c6reGNs.
* Second, i just want to introduce myself: I am doing my master thesis
at the Vienna University of Technology about the benefit of AR
compared to paper based approaches in tourist navigation and
exploration scenarios.
As part of this thesis i would like to enrich mixare with some things:
* A more sexy UI
* Social media messages in the sky instead of the horizontal plane
* Navigation aids
* Perhaps some cartographic generalization algorithms to improve
perception
Perhaps a fork on github would be a good idea, because there are some
fundamental changes. What do you think?
Thats it for now, and thanks for this great open source app.
Greetings,
Hannes
Joshua Eckroth
Hi Hannes,
Thanks so much for working on Mixare! I'm experimenting with adapting
Mixare for my own apps, so any more code written by others just ends up
helping me :)
Because git makes forking super easy, a fork is always a good idea.
Whatever should be incorporated back into Mixare proper can be
cherry-picked from your development tree. Forking also allows other
developers and users to track independent lines of development, and
cherry-pick themselves.
Thanks,
-josh
Julio Faerman
I am also working on my master's and wanting to develop it on mixare.
If you can make your fork public and add just enough documentation so that others can read your code, i think that would help (well, at least it would help me :))
Thanks for your contribution and best of luck
Julio
--
You received this message because you are subscribed to the Google
Groups "mixare-development" group.
To post to this group, send email to mixare-de...@googlegroups.com
To unsubscribe from this group, send email to
mixare-developm...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/mixare-development?hl=en
The project's home page is at http://www.mixare.org/en
Daniele Gobbetti - Peer internet solutions
> Hello everyone,
Hello Hannes, welcome to the list!
> Two things:
>
> * First, i just added Google Buzz as a data source. Patch here:
> http://pastebin.com/raw.php?i=2c6reGNs.
Thanks a lot for your patch! Expect to see it in the svn soon :)
For future patches, feel free to use the issue tracker at
http://code.google.com/p/mixare/issues/list
so that it's easier for everyone to follow the progresses.
> * Second, i just want to introduce myself: I am doing my master thesis
> at the Vienna University of Technology about the benefit of AR
> compared to paper based approaches in tourist navigation and
> exploration scenarios.
>
> As part of this thesis i would like to enrich mixare with some things:
>
> * A more sexy UI
> * Social media messages in the sky instead of the horizontal plane
> * Navigation aids
> * Perhaps some cartographic generalization algorithms to improve
> perception
Wow! Sounds wonderful, looking forward to the further developments.
By the way, since it looks like there are (quite) a lot of people
working on mixare, we would like to give you additional privileges to
the issue tracker (as Miriam has) to help you dealing with your thesis,
anyone interested please drop us a line at in...@mixare.org !
> Perhaps a fork on github would be a good idea, because there are some
> fundamental changes. What do you think?
We have nothing against it. I have little experience with git as RCS, I
would like to keep the svn history when moving, do you have any
experience wrt this aspect?
> Thats it for now, and thanks for this great open source app.
The best is to watch the community growing! :)
> Greetings,
> Hannes
Regards,
Daniele
--
Daniele Gobbetti - Peer internet solutions
> Hi Hannes,
>
> Thanks so much for working on Mixare! I'm experimenting with adapting
> Mixare for my own apps, so any more code written by others just ends up
> helping me :)
Joshua (and all) please remember that mixare is GPL3. We would love to
see additional application built on top of it, and will ensure that the
license is honored!
> Because git makes forking super easy, a fork is always a good idea.
> Whatever should be incorporated back into Mixare proper can be
> cherry-picked from your development tree. Forking also allows other
> developers and users to track independent lines of development, and
> cherry-pick themselves.
See my previous answer, if you have experience in importing an svn
project in GIT while keeping the history I would love to have some
directions. Thanks a lot.
I also would like to discuss the pros and cons of different "providers"
(eg. github) and RCS. We have the choice to switch the google project to
mercurial instead of SVN. It would be better to keep the code and the
project wiki in the same place, but I understand that the list favors
git over mercurial...
What do you think?
>
> Thanks,
> -josh
>
Best regards,
DAniele
--
Joshua Eckroth
> Il 26/07/2010 15:20, Joshua Eckroth ha scritto:
>> Hi Hannes,
>>
>> Thanks so much for working on Mixare! I'm experimenting with adapting
>> Mixare for my own apps, so any more code written by others just ends up
>> helping me :)
>
> Joshua (and all) please remember that mixare is GPL3. We would love to
> see additional application built on top of it, and will ensure that
> the license is honored!
Yes, I'm aware! :) Nothing has been released (or even seriously
developed) yet.
>> Because git makes forking super easy, a fork is always a good idea.
>> Whatever should be incorporated back into Mixare proper can be
>> cherry-picked from your development tree. Forking also allows other
>> developers and users to track independent lines of development, and
>> cherry-pick themselves.
>
> See my previous answer, if you have experience in importing an svn
> project in GIT while keeping the history I would love to have some
> directions. Thanks a lot.
>
> I also would like to discuss the pros and cons of different
> "providers" (eg. github) and RCS. We have the choice to switch the
> google project to mercurial instead of SVN. It would be better to keep
> the code and the project wiki in the same place, but I understand that
> the list favors git over mercurial...
>
> What do you think?
Well git vs. SVN vs. Mercurial vs. et al. is always a heated debate. I'm
quite fond of git, and likewise GitHub, which has issues & wiki & commit
log, but that's just me. I think GitHub is a huge player in the open
source development field and would give your project bigger awareness in
the community. It's easy to track projects on GitHub, easy to fork them,
etc.
It's easy to import SVN history to a git repository:
http://help.github.com/svn-importing/ (also see "Other guides" at the
bottom)
I think Mercurial is not a good choice; in the distributed RCS field, I
think git is really the only player. But again, this is just opinion!
-josh
Daniele Gobbetti - Peer internet solutions
> Hi Hannes,
>
> I am also working on my master's and wanting to develop it on mixare.
> If you can make your fork public and add just enough documentation so
> that others can read your code, i think that would help (well, at least
> it would help me :))
> Thanks for your contribution and best of luck
Hi Julio, hi all,
we expect to see the developments in the public, please help us to help
you :) We are open to suggestions and would like to make the
collaboration as easy as possible!
>
> Julio
Best,
Daniele
--
> <mailto:mixare-de...@googlegroups.com>
> To unsubscribe from this group, send email to
> mixare-developm...@googlegroups.com
> <mailto:mixare-development%2Bunsu...@googlegroups.com>
Daniele Gobbetti - Peer internet solutions
> On 7/26/2010 10:57 AM, Daniele Gobbetti - Peer internet solutions wrote:
>> Il 26/07/2010 15:20, Joshua Eckroth ha scritto:
>>> Hi Hannes,
>>>
>>> Thanks so much for working on Mixare! I'm experimenting with adapting
>>> Mixare for my own apps, so any more code written by others just ends up
>>> helping me :)
>>
>> Joshua (and all) please remember that mixare is GPL3. We would love to
>> see additional application built on top of it, and will ensure that
>> the license is honored!
>
> Yes, I'm aware! :) Nothing has been released (or even seriously
> developed) yet.
>
Something related that may be of interest for everyone: we would like to
give more visibility to apps built on top of mixaare / additional data
sources / custom launchers inside mixare itself. Please let us know
about your work!
>> I also would like to discuss the pros and cons of different
>> "providers" (eg. github) and RCS. We have the choice to switch the
>> google project to mercurial instead of SVN. It would be better to keep
>> the code and the project wiki in the same place, but I understand that
>> the list favors git over mercurial...
>>
>> What do you think?
>
> Well git vs. SVN vs. Mercurial vs. et al. is always a heated debate. I'm
> quite fond of git, and likewise GitHub, which has issues & wiki & commit
> log, but that's just me. I think GitHub is a huge player in the open
> source development field and would give your project bigger awareness in
> the community. It's easy to track projects on GitHub, easy to fork them,
> etc.
Well wiki and issues are already on the google page of the project and I
think this should not change (unless the features provided by github are
much better than those provided by google code).
> It's easy to import SVN history to a git repository:
> http://help.github.com/svn-importing/ (also see "Other guides" at the
> bottom)
Good to know, I know that google SVN contains the history of the whole
project (wiki pages, download, etc.) but I guess you can filter those out...
> I think Mercurial is not a good choice; in the distributed RCS field, I
> think git is really the only player. But again, this is just opinion!
Understood: git 1 - mercurial 0 :)
Thanks for sharing your experience!
> -josh
Reagards,
Daniele
--
Hannes Boran
Actually, i just have experience with cvs and svn, but from what i
have heard, git and github shall be a big step forward.
I think, i will do a fork on github for my development line and we can
experiment with git and then see if this fits for the hole project.
Some privileges for the issue tracker would be nice.
-hannes
On 26 Jul., 17:21, Daniele Gobbetti - Peer internet solutions
Daniele Gobbetti - Peer internet solutions
> Hi Daniele, Joshua and Julio!
>
> Actually, i just have experience with cvs and svn, but from what i
> have heard, git and github shall be a big step forward.
> I think, i will do a fork on github for my development line and we can
> experiment with git and then see if this fits for the hole project.
Hello Hannes,
I merged your patch in the repository. I also created an issue first:
http://code.google.com/p/mixare/issues/detail?id=30
So that your code is linked to the appropriate svn revision.
I added you as contributor to mixare, and you may edit issues in the
issue tracker now.
I ask you to wait before creating the github project, I would like to
reach consensus on the list and then proceed. I hope we will be able to
switch (or decide to keep SVN) before the end of the week.
> Some privileges for the issue tracker would be nice.
>
> -hannes
Best,
Daniele
--
>>> quite fond of git, and likewise GitHub, which has issues& wiki& commit
>>> log, but that's just me. I think GitHub is a huge player in the open
>>> source development field and would give your project bigger awareness in
>>> the community. It's easy to track projects on GitHub, easy to fork them,
>>> etc.
>>
>> Well wiki and issues are already on the google page of the project and I
>> think this should not change (unless the features provided by github are
>> much better than those provided by google code).
>>
>>> It's easy to import SVN history to a git repository:
>>> http://help.github.com/svn-importing/(also see "Other guides" at the
>>> bottom)
>>
>> Good to know, I know that google SVN contains the history of the whole
>> project (wiki pages, download, etc.) but I guess you can filter those out...
>>
>>> I think Mercurial is not a good choice; in the distributed RCS field, I
>>> think git is really the only player. But again, this is just opinion!
>>
>> Understood: git 1 - mercurial 0 :)
>> Thanks for sharing your experience!
>>
>>> -josh
>>
>> Reagards,
>> Daniele
>>
>> --
>
--
==============================
> Daniele Gobbetti
> Usability & Innovation Management
>
> Peer GmbH/Srl
> www.peer.biz
> Tel. +39 0471 631080
> Fax +39 0471 631724
Hannes Boran
here. I meant to make a fork for me, so i can develop my stuff and do
not interfere with your development. And if there is something you can
use from me, you could then cherry-picking like Joshua said.
Initially I didn't meant that you should put the original ("your")
project to github, although that would be even better.
Regards,
Hannes
On 27 Jul., 11:38, Daniele Gobbetti - Peer internet solutions
Julio Faerman
Joshua Eckroth
I think the choice should only be between SVN and git. The reason is these are clearly* more popular in the open source world than Mercurial or any of the others (except maybe CVS, but nobody wants to use that anymore anyway). The fact that Google Code does not support git is, firstly, very uncool, but secondly one reason not to switch to git.
However, SVN is not friendly for scattered open source development. It's hard to fork an SVN project, and it's hard to import changes from others. It's especially hard for developers (possibly people you don't even know about) to grab a copy of the source, make some changes on their own box just to try ideas (and build a history of these changes in their private repo), and then tell the world about these changes so that they may be incorporated. With SVN, "commit access" has to be managed, which introduces a bottleneck and bureaucracy to the development process. I feel that, in the end, experimentation and collaboration is limited with SVN (and centralized VCS) as compared to something like git (and Mercurial, but again, Mercurial just is not popular enough). But maybe I'm just trying to be a hipster! Hopefully we can discuss this more.
* I say "clearly" just from experience. I just don't feel any "buzz" over Mercurial. I was dedicated to it a few years ago, but it felt a bit lonely. I was recently at a Perl conference; there were talks about git, not a word about Mercurial. In the git talks, SVN was mentioned a lot. Also, GitHub is a rising star, I think, in the open source development world, and is additionally used by a lot of companies (with private repositories). SVN is old enough to be entrenched, which also makes it a good choice.
In the final analysis, what matters most is what the Mixare leaders want (and what tools they are comfortable using) and what kind of image they want to project ("how open to forking and collaboration are we?"). Individual developers can use git in "hostile" (non-git) environments just fine. For example, say someone has SVN commit access. That person could use git on his or her machine to pull SVN updates, record intermediate changes and create forks for quick experiments, then choose what change-history (what personal fork) to commit to SVN. This is the git-svn tool. Thus, if a developer wants to use git, that developer can do so. The question is, what do the Mixare developers want to support "natively," and what image does SVN project vs. the image git projects?
-josh