You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Tim Van Steenburgh <va...@users.sf.net> on 2014/01/02 22:21:10 UTC
[allura:tickets] Re: #6896 Developer architecture docs
1. Yeah, I'll update that code.
2. Definitely, I'll do these as soon as this is published.
3. What do you think about using the SF link for now? Seems like we need to either do that, or setup git on the apache server. Not sure what's involved there, or how much work it'll be.
---
** [tickets:#6896] Developer architecture docs**
**Status:** in-progress
**Labels:** docs
**Created:** Tue Nov 19, 2013 08:28 PM UTC by Dave Brondsema
**Last Updated:** Thu Jan 02, 2014 09:16 PM UTC
**Owner:** Tim Van Steenburgh
It'd be useful to have some high-level docs for developers that are getting started with Allura. And update/overhaul our current developer-oriented doc pages. I think we should cover things like: how the code is organized, what technology is used (paster, TG, EW, jinja, etc), how to log & debug, how tests work, etc.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: #6896 Developer architecture docs
Posted by Dave Brondsema <br...@users.sf.net>.
Perhaps just omit that section from the docs for now? We don't have very frequent new contributors so it may be fine for a while. Folks can come and ask if/when they get to that point
---
** [tickets:#6896] Developer architecture docs**
**Status:** in-progress
**Labels:** docs
**Created:** Tue Nov 19, 2013 08:28 PM UTC by Dave Brondsema
**Last Updated:** Thu Jan 02, 2014 09:16 PM UTC
**Owner:** Tim Van Steenburgh
It'd be useful to have some high-level docs for developers that are getting started with Allura. And update/overhaul our current developer-oriented doc pages. I think we should cover things like: how the code is organized, what technology is used (paster, TG, EW, jinja, etc), how to log & debug, how tests work, etc.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: #6896 Developer architecture docs
Posted by Dave Brondsema <br...@users.sf.net>.
3\. The SF repo is currently hidden to non-admins. I did that a few weeks ago, to reduce confusion/duplication. We could use it again though. Setting up git on the apache server would be better I think, but would take some work. And probably some customization so that the /p/allura repo path and checkout command can be different from forks in /u/*
---
** [tickets:#6896] Developer architecture docs**
**Status:** in-progress
**Labels:** docs
**Created:** Tue Nov 19, 2013 08:28 PM UTC by Dave Brondsema
**Last Updated:** Thu Jan 02, 2014 09:16 PM UTC
**Owner:** Tim Van Steenburgh
It'd be useful to have some high-level docs for developers that are getting started with Allura. And update/overhaul our current developer-oriented doc pages. I think we should cover things like: how the code is organized, what technology is used (paster, TG, EW, jinja, etc), how to log & debug, how tests work, etc.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.