Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Website gives the impression the project is dead. #22

Open
tshirtman opened this issue Mar 28, 2013 · 5 comments
Open

Website gives the impression the project is dead. #22

tshirtman opened this issue Mar 28, 2013 · 5 comments

Comments

@tshirtman
Copy link

Last news is from 2010, and the switch to git is not reflected (documentation points to fossil installation and so on), part of the links in «what's built with lamson» list are dead, only the redirection from support.lamson.org gets you there to learn the project is indeed not dead.

Is the website hard to update, is Zed too busy with other things? Are contribution in this area needed (no promise i would, but good to know) or are there other things preventing the project to thrive?

@tino
Copy link
Contributor

tino commented Apr 1, 2013

Jep, it appears so. As it sais in the redirect form support.lamsonproject.org: Pull requests accepted, although I am overloaded a bit so may be slow

@gjedeer
Copy link

gjedeer commented May 17, 2013

I'm a newcomer to Lamson and I was just going to report that issue. I came here to look if the project is dead and the change log on git was last updated 3 years ago. The website has last news from 2010 too. Yet there's a version on March in the cheese shop. Where should one look for some kind of change log?

@andreif
Copy link

andreif commented Jul 26, 2013

@gjedeer it is hard to tell how you managed to miss all the latest commits in the log.

@gjedeer
Copy link

gjedeer commented Jul 28, 2013

It's pretty easy to miss.

https://github.com/zedshaw/lamson/blob/master/ChangeLog

@andreif
Copy link

andreif commented Jul 28, 2013

@gjedeer Ah, that one. Then hard to argue :) I am sure if someone wants to take care of the project while @zedshaw is working hard somewhere, that person could get collaborator rights for the repo. Otherwise, I would just look around in the network and merge valuable commits into my fork.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants