Special User Sections > Site/Forum Features

NANY 2011 :: A New Concept -- Have your say!

<< < (12/14) > >>

Perry Mowbray:
I had suggested a summer event, that ran from June till the end of August, with the wrap-up in early September, followed by a reminder that NANY is on the way. I figured the entire summer would be great for coding more substantial things and it wouldn't clash with things like major holidays and exams.-app103 (April 19, 2010, 11:34 AM)
--- End quote ---

I (and I think we) liked that suggestion, and is pretty much the proposal, just not as formalised. That type of arrangement, where the entrant decides on their own level of participation, has a lot of advantages (as mouser has said) -- and having the main work not clashing with holidays is very important (if we're wanting "main work" to happen).

From the surveys: having more time to do more substantial entries was a significant issue. That has been my main push, as a response to those requests.

Perry Mowbray:
I hear ya.. though i guess what i had in mind was still preserving the mad dash for people to create new programs at the end of the year.. while still recognizing those who had created stuff earlier in the year, and celebrating them all at an end-of-year wrap-up.
-mouser (April 19, 2010, 05:15 PM)
--- End quote ---

This was how it was discussed previously: a bit like a newsletter thing --

* Here are the NANY "winners"
* Also released this year...
One of the biggest reasons for this is that NANY does attract attention, and it's not a bad place to also mention some of the other completions we've had here too. So the NANY wrap-up is a celebration, and caught up in that celebration are the other things that have happened through the year.  :)

Also: Let's not forget that a "mad dash" can be more than a month and not everyone wants their entry to be just what they can do in a month, they'd prefer extra time.

Gothi[c]:
Some of the reasons that Entrants didn't set up RedMine:

    * I didn't want to have to deal with learning how to do RedMine while I was concentrating on getting my project completed.
    * I wouldn't know what to do with it.
    * Forgot
    * I've waned to use Mercurial CVS integration but it did not work.

--- End quote ---

Mercurial integration requires a mercurial account on the server, which should be requested through me.
We didn't have this setup until yesterday, when ewemoa requested it. :)
To address the issues I have created a page which summaries the features we offer on the member server, and a page with some basic mercurial help. :

https://admin.dcwing.com/services/

Eventually, perhaps a wiki would be a better format for all of that, but it's better than nothing for now. :)

<edit>
For clarity, if you read over the mercurial help page link on the services page, here is a direct link :

https://admin.dcwing.com/services/mercurial.html

</edit>

ewemoa:
For clarity, if you read over the mercurial help page link on the services page, here is a direct link :

https://admin.dcwing.com/services/mercurial.html
-Gothi[c] (April 21, 2010, 01:47 PM)
--- End quote ---

Thanks for the mercurial set up and the summary :)

digression: some mercurial related infoI found it helpful to configure the hgrc file within a repository (so <repos-dir>/.hg/hgrc) with auth info.  Specifically, adding the following sort of section:


--- ---[auth]
something.prefix=https://admin.dcwing.com/
something.username=appropriateusername
something.password=appropriatepassword

Where "something" , "appropriateusername", and "appropriatepassword" should be filled in for your case.

It seems there's a relevant posting at StackOverflow, so here's a pointer to that:

  http://stackoverflow.com/questions/2584407/how-to-save-username-and-password-with-mercurial

(The top response had a pointer to a page from http://hgtip.com/ which seems like it might be generally handy.)

May be Gothi[c] can scold me if this sort of set-up is a no-no :)

(I'm using mercurial through an upgraded installation of an old "portable" cygwin.)

Gothi[c]:
I found it helpful to configure the hgrc file within a repository (so <repos-dir>/.hg/hgrc) with auth info.  Specifically, adding the following sort of section

--- End quote ---

It's not a no-no, but I find manually typing out the http authentication cleaner, also because the password is not as plaintext in your hgrc.

On the server side Mercurial will take the username you logged in with from the httpd authentication, so you can use something like:

[web]
  allow_push = someuser

Which is what I use to define which httpauth users are allowed to upload (write access)

If you really hate copy/pasting a password, and don't mind the plaintext password in a file, then that's definitively OK :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page