You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Gavin McDonald <ga...@16degrees.com.au> on 2012/02/01 00:05:15 UTC
Project Website
The thread 'Editing the bloodhound website' is actually about editing the
projects Status page at incubator.apache.org/projects/bloodhound.html
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?
Gav...
Re: Project Website
Posted by Gary <ga...@wandisco.com>.
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<ga...@16degrees.com.au> wrote:
>>
>>> -----Original Message-----
>>> From: Greg Stein [mailto:gstein@gmail.com]
>>> Sent: Wednesday, 1 February 2012 11:41 AM
>>> To: bloodhound-dev@incubator.apache.org; gavin@16degrees.com.au
>>> Subject: Re: Project Website
>>>
>>> On Tue, Jan 31, 2012 at 18:05, Gavin McDonald<ga...@16degrees.com.au>
>>> 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
Re: Project Website
Posted by Mark Poole <ma...@wandisco.com>.
I have already created a design (see previous list email) but text
suggestions for it would be cool.
I'm going to put it up early next week.
On 1 Feb 2012, at 17:49, Joachim Dreimann <jo...@wandisco.com> wrote:
> I have now replaced the "Everything you need to run Bloodhound will be
> provided within." with "Everything you need to run Bloodhound with
> your favourite web server and database will be provided." and changed
> the sentence before form "easy to use installer" to "easy
> installation process".
>
> http://dl.dropbox.com/u/59840506/Bloodhound/HTML/index.html
>
> What does everybody think?
>
> - Joe
Re: Project Website
Posted by Greg Stein <gs...@gmail.com>.
Ah. Right. Forgot about that part :-P
On Wed, Feb 1, 2012 at 13:49, Joe Dreimann
<jo...@wandisco.com> wrote:
> I agree Greg. However I don't have commit access, this is a workaround until I do.
>
> As these files don't exist in svn I can't produce patches against them with updates either, which was suggested to me regarding the wireframes.
>
> I'd have to Email a current committer with the files every time, and on an average day I may work on 15 or so files. In fact my lack of commit access is why the other 25 Mockups aren't in svn yet.
>
> Long story short, with commit access I would do all my work in svn. :)
>
> ________________________
> @jdreimann - Twitter
> Sent from my phone
>
> On 1 Feb 2012, at 18:32, Greg Stein <gs...@gmail.com> wrote:
>
>> On Wed, Feb 1, 2012 at 12:48, Joachim Dreimann
>> <jo...@wandisco.com> wrote:
>>> I have now replaced the "Everything you need to run Bloodhound will be
>>> provided within." with "Everything you need to run Bloodhound with
>>> your favourite web server and database will be provided." and changed
>>> the sentence before form "easy to use installer" to "easy
>>> installation process".
>>>
>>> http://dl.dropbox.com/u/59840506/Bloodhound/HTML/index.html
>>>
>>> What does everybody think?
>>
>> If you ask us what we think, then we have to respond in email and wait
>> for you to update your draft.
>>
>> It is better to just check your work into source control. That allows
>> others in the community to tweak and alter the website. ie. move away
>> from a dependency on you, to enabling the community as a whole to make
>> changes.
>>
>> Please just commit your work. My feedback will done via svn.
>>
>> In general, I'd like to see more work done in version control rather
>> than on personal websites (such as people.apache.org or dropbox). When
>> it is in version control, then we can all participate. Newcomers can
>> also find the work in version control much easier than tracking down
>> these personal sites based on links found in some random email on the
>> mailing list.
>>
>> Thanks,
>> -g
Re: Project Website
Posted by Joe Dreimann <jo...@wandisco.com>.
I agree Greg. However I don't have commit access, this is a workaround until I do.
As these files don't exist in svn I can't produce patches against them with updates either, which was suggested to me regarding the wireframes.
I'd have to Email a current committer with the files every time, and on an average day I may work on 15 or so files. In fact my lack of commit access is why the other 25 Mockups aren't in svn yet.
Long story short, with commit access I would do all my work in svn. :)
________________________
@jdreimann - Twitter
Sent from my phone
On 1 Feb 2012, at 18:32, Greg Stein <gs...@gmail.com> wrote:
> On Wed, Feb 1, 2012 at 12:48, Joachim Dreimann
> <jo...@wandisco.com> wrote:
>> I have now replaced the "Everything you need to run Bloodhound will be
>> provided within." with "Everything you need to run Bloodhound with
>> your favourite web server and database will be provided." and changed
>> the sentence before form "easy to use installer" to "easy
>> installation process".
>>
>> http://dl.dropbox.com/u/59840506/Bloodhound/HTML/index.html
>>
>> What does everybody think?
>
> If you ask us what we think, then we have to respond in email and wait
> for you to update your draft.
>
> It is better to just check your work into source control. That allows
> others in the community to tweak and alter the website. ie. move away
> from a dependency on you, to enabling the community as a whole to make
> changes.
>
> Please just commit your work. My feedback will done via svn.
>
> In general, I'd like to see more work done in version control rather
> than on personal websites (such as people.apache.org or dropbox). When
> it is in version control, then we can all participate. Newcomers can
> also find the work in version control much easier than tracking down
> these personal sites based on links found in some random email on the
> mailing list.
>
> Thanks,
> -g
Re: Project Website
Posted by Greg Stein <gs...@gmail.com>.
On Wed, Feb 1, 2012 at 12:48, Joachim Dreimann
<jo...@wandisco.com> wrote:
> I have now replaced the "Everything you need to run Bloodhound will be
> provided within." with "Everything you need to run Bloodhound with
> your favourite web server and database will be provided." and changed
> the sentence before form "easy to use installer" to "easy
> installation process".
>
> http://dl.dropbox.com/u/59840506/Bloodhound/HTML/index.html
>
> What does everybody think?
If you ask us what we think, then we have to respond in email and wait
for you to update your draft.
It is better to just check your work into source control. That allows
others in the community to tweak and alter the website. ie. move away
from a dependency on you, to enabling the community as a whole to make
changes.
Please just commit your work. My feedback will done via svn.
In general, I'd like to see more work done in version control rather
than on personal websites (such as people.apache.org or dropbox). When
it is in version control, then we can all participate. Newcomers can
also find the work in version control much easier than tracking down
these personal sites based on links found in some random email on the
mailing list.
Thanks,
-g
Re: Project Website
Posted by Joachim Dreimann <jo...@wandisco.com>.
I have now replaced the "Everything you need to run Bloodhound will be
provided within." with "Everything you need to run Bloodhound with
your favourite web server and database will be provided." and changed
the sentence before form "easy to use installer" to "easy
installation process".
http://dl.dropbox.com/u/59840506/Bloodhound/HTML/index.html
What does everybody think?
- Joe
Re: Project Website
Posted by Joachim Dreimann <jo...@wandisco.com>.
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 <ga...@16degrees.com.au> wrote:
>
>
>> -----Original Message-----
>> From: Greg Stein [mailto:gstein@gmail.com]
>> Sent: Wednesday, 1 February 2012 11:41 AM
>> To: bloodhound-dev@incubator.apache.org; gavin@16degrees.com.au
>> Subject: Re: Project Website
>>
>> On Tue, Jan 31, 2012 at 18:05, Gavin McDonald <ga...@16degrees.com.au>
>> 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
>
RE: Project Website
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Greg Stein [mailto:gstein@gmail.com]
> Sent: Wednesday, 1 February 2012 11:41 AM
> To: bloodhound-dev@incubator.apache.org; gavin@16degrees.com.au
> Subject: Re: Project Website
>
> On Tue, Jan 31, 2012 at 18:05, Gavin McDonald <ga...@16degrees.com.au>
> 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
Re: Project Website
Posted by Greg Stein <gs...@gmail.com>.
On Tue, Jan 31, 2012 at 18:05, Gavin McDonald <ga...@16degrees.com.au> 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.
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?
Cheers,
-g