I'm not sure that we would say that "Everything you need to run
Bloodhound will be provided within." as that might imply that we have
the full stack covered.
Otherwise that is very good I think. Certainly looks good to me.
Cheers,
Gary
On 02/01/2012 04:43 PM, Joachim Dreimann wrote:
I have spent an hour this afternoon setting up a site I suggest would
work as a placeholder for now. I skipped the mockup and went straight
to html.
You can view the result in my public Dropbox folder:
http://dl.dropbox.com/u/59840506/Bloodhound/HTML/index.html
Just to be clear, this is only to replace the following page:
http://incubator.apache.org/bloodhound/
The "Learn more>" button links straight to the Bloodhound instance
set up for the project at:
https://issues.apache.org/bloodhound/
It's put together with simply one HTML page and the Bootstrap CSS file
that we've already discussed in the other bloodhound-dev@ mail thread
regarding UI basics.
Does this need a footer, or any major changes before someone could commit it?
- Joe
On 1 February 2012 08:30, Gavin McDonald<[email protected]> wrote:
-----Original Message-----
From: Greg Stein [mailto:[email protected]]
Sent: Wednesday, 1 February 2012 11:41 AM
To: [email protected]; [email protected]
Subject: Re: Project Website
On Tue, Jan 31, 2012 at 18:05, Gavin McDonald<[email protected]>
wrote:
The thread 'Editing the bloodhound website' is actually about editing
the projects Status page at
incubator.apache.org/projects/bloodhound.html
That thread also morphed into editor the project's website, and Mark
posted
an example. Nothing has been checked in regarding that example, though.
This thread is about the actual website we intend to use at
http://incubator.apache.org/bloodhound/
That page is blank, there needs to be something there, is it being
worked on, is there something I need to be doing?
Well... that website is checked out from trunk/website/, but I think two
things needed to happen:
1) Move that to incubator/bloodhound/site/ (rather than
incubator/bloodhound/trunk/website/). The "site" name is more typical, and
it should be a sibling of trunk, since (typically) trunk is what we
ship/release.
The website shouldn't (IMO) be part of that.
Done,
2) Hook .../site/ into svnpubsub so people don't have to log into
people.a.o.
Would you be able to get that stuff hooked up?
Yep, all done (as you saw).
So, anyone who wants to update the website, just commit to svn at
bloodhound/site and
within a few seconds just refresh your browser at
incubator.apache.org/bloodhound to see
your content already there.
HTH
Gav...
Cheers,
-g
