API Docs
Whit
Ari Brown
On Nov 14, 2011, at 7:07 PM, Whit wrote:
> The API links return a 404. Is there any chance if them returning?
You got a link for me to look at that contains the link to the 404?
Also, amp is no longer active. We gave it a good shot, and learned a lot from doing it, but this iteration of it is over. Feel free to use what we have (I know I sometimes do), but in the distant future, I'd like to take another stab at it. Ideally, it would be funded as a RSOC project, but now that libgit is out, I don't think that will happen. Oh well. C'est la vie.
- Ari
Alan Franzoni
> Also, amp is no longer active. We gave it a good shot, and learned a lot from doing it, but this iteration of it is over. Feel free to use what we have (I know I sometimes do), but in the distant future, I'd like to take another stab at it. Ideally, it would be funded as a RSOC project, but now that libgit is out, I don't think that will happen. Oh well. C'est la vie.
What made AMP interesting in my eyes was not the fact of "having an
implementation of VCS XXXX in Ruby", but the fact that it allowed a
scriptable workflow on the top of any VCS.
IMHO the backend part would work nicely even by just spawning VCS
commands every time.
On the contrary, many times a development team has difficulties at
estabilishing a workflow, because not every team member has a good
inside knowdlege on VCS. Many of them would just like an interface like
"start a new feature called FooBar"
"do this on FooBar"
"do that on FooBar"
"FooBar is done"
and then amp could be used to map such "high level functional
requirements" to low level VCS commands.
If anybody is interested in working on that part, contact me, I'd like
to carry on some work on such a project.
--
Latest blog post: Deploying WAR on Heroku http://t.co/M4krW2Mu
contact me at public@[mysurname].eu
Ari Brown
On Nov 15, 2011, at 10:33 AM, Alan Franzoni wrote:
> <snip>
> If anybody is interested in working on that part, contact me, I'd like
> to carry on some work on such a project.
You have a great point for the advocation for amp. After amp had noticeably slowed, Mike and I talked about what went wrong in it, just to debrief. One of the biggest problems we felt we had was that we conflated interface (the amp frontend that you enjoy) with implementation (hg and git rewritten).
I'd be willing to give it another shot with you, Alan, but I'd have to wait until school's over in later April. If you can wait till then, that'd be awesome. Up until then we could work on having a solid plan before attacking this again.
- Ari
Whit
interesting in working on this project as well. I'm emailing you both
the email address that I use.