Cheers
Stephan

I would be glad to get it added the CentOS Extras repository when it is working.

Please continue to add comments, and feel free to tackle some of the key elements of this project (if it were to be continued) such as what language it would be coded in (Java, due to its portability? C#, for the same reason? Another language altogether?), how certain mechanisms such as encryption would work, and the like.

Finally, if you are a developer or documentation writer and would be willing to dedicate some time to this project if it were continued, please state which language you know (in both cases :)) and what kind of a role you would like to play in its development.

Again, if there is enough demand (and there certainly seems to be!), I will take care of setting up the project, its website, etc and organising the developers. And, if we decided to code it in a language I know or am learning, I’d be more than willing to help out with its development as well.

http://www.novell.com/collateral/4621351/4621351.html

I believe it is currently only available for Netware and their OES Linux, but should be ported over onto SLES in the near future. The interesting bit is the fact that the I-Folder part of the application is already open source.
I-Folder and the directory service are pretty much what this whole application are built on.
Maybe Novell could be persuaded to open up some more of this code. However I doubt they will ever release the edirectory code.
Or at least the I-Folder code could be starting point for a seperate application.
Just a thought, please don’t flame me to badly I left my asbestos suit at home.

iFolder might be a good starting point, but it would have to be integrated well with this project and that would probably result in the branching of iFolder into two - iFolder, and the version implemented in this project.

Thank you for the suggestion - iFolder will be considered if/when we get a team together

magikfingerz - Thank you for bringing Lucane to my attention. I have taken a quick look at it and I have a few things to say about it (although I haven’t yet been able to get it working on my Linux desktop):

• From the screenshots, its interface looks fairly antiquated and is not as intuitive as I would like it to be. However, I think this may be due, in part, to its Java base.
• However, it does look fairly complete in terms of its features - everything except its handling of shared files. Filesharing would be a key part of this project, so it may be hard (or not, it depends on Lucane’s code) to integrate an existing version control system on top of this technology.

I really like the look of Lucane, but I think it may be best to start afresh, perhaps in another language, and use it as another example upon which we have to improve.

I think we should start afresh for a few reasons:

• It allows us to lay out clear guidelines and visions so that our project does not end up deceased like Lucane and so that we strive to build an easier-to-use, more intuitive groupware platform than anyone else.
• New minds can give different takes on the functionality and usability of the platform so that it’s a viable option to enterprises, organizations and users seeking such a product.
• We can decide on the most suitable language for the job. One which is cross-platform, has a powerful, simple and Open Source GUI toolkit and a good Open Source IDE (I believe that Lucane’s developers were using a proprietary IDE) available for it and which will allow us to reach our goals as closely as possible.

If there are no objections, I shall set up a separate project on SourceForge and put up a forum for us to discuss the intricacies of the platform. Even if we do end up using Lucane as a base, we can give it a completely new name and decide how we’re going to change it to make it better than before.

And now, to decide on a good name for this project

kc - Thank you too for offering to help.

Abby Normal - Haha! Well, you may be slightly surprised by the name I’ve chosen for it… I’m about to post about that - give me fifteen minutes

The reason Groove can use P2P is that Microsoft has no trouble setting up a few public servers to maintain databases of registered clients and their IP address, which is required for P2P to work properly (especially when those collaborating are not on the same subnet). I think this would be more difficult for an Open Source project unless we gathered significant funding to run the servers and pay for the pipes.

This is why I proposed the client/server model - not only does it make it much easier to build on top of current version control systems, but that server can also maintain the database of who has yet to read a certain new event or file, messages which have been sent to colleagues who are not yet online, etc. I think the client/server model is more powerful, in this case, than P2P, and would allow Groove to have greater functionality. However, I do see your point about the server being a single point of failure - not only is all your data exposed if it is compromised (unless there are strict security policies and mechanisms enforcing those policies in place), but everyone suffers a loss of availability if that server goes offline for a certain period of time, no matter what the reason.

If Mira Groupware gets accepted for SourceForge hosting, I’ll set up a wiki on its website - that will allow us to document our thoughts in a clearer way and to choose which of the options to implement

- I barely use office applications (and thus will not pay M$ scorchingly high prices for their Office suite);
- and since M$ will probably make a big mess mixing these two very different things together as one can only guess.

Not to mention that all other platforms (like Mac OSX and Linux) that the Groove team was developing back in 2004 were abandoned for obvious reasons after the M$ acquisition. And that is a big problem for my team, since we all use different development platforms (like Mac OSX and Linux) but we have to keep Windows machines mainly because of Groove.

If this project is serious about developing a trully multi-platform open source Groove alternative I would be happy to get involved (I know a lot of people that would to).

Thanks
Rajesh Akkineni

A shame because it is a pretty good “copy” of Groove 2007.

Nude Pictures Of Old Women And Men…

Somas. Somas with carisoprodol doese t contain codeine. Do somas show up in aurine test. Somas do they have codeine in them….

Tramadol side effects. Tramadol. Comparative potencies of opioids tramadol….

Xanax valium. No rx online xanax. Psyweb xanax. Xanax. Xanax side effects. Ativan xanax valuim trial pack….

Cheapest airfare for cheapskates….

So I am assessing Collaber, CipherShare & TUTOS … if anyone knows of any others that I might use for document collaboration please let us know!