Re: [opennic-discuss] Project - Re-Vamped Glue Website

Anner van Hardenbroek wrote:
> Let's dig deeper in this matter. I'd like to do the programming work, but
> you have no expectation that it's done in a flip of a finger. It costs much
> time. I'd like to purpose Qcodo and my in-house framework to build on top
> of. I'm absolutely not an artist so the HTML have to be designed by someone
> else. But before I can and want to begin development of the glue site, there
> has to be a more concrete plan. So lets define an must-have and like-to-have
> list of features.

Thank you Anner for offer your help. It is very appreciated. Also thank 
you very much for explaining the framework.

I have a few questions to kick things off on this discussion. The first 
one is;

You explained alot about the framework and what not. I am not a 
programmer, so I did not have a full understanding of what you were 
explaining. So what I would like to know, is what will this framework 
offer us?

Have you read the project page on the wiki? If so were my thoughts on 
how I would like the site clear? I have explained in previous emails 
what I would like the end site to be, and the goals for it.

The last thing is Anner, I would like you to take lead on this project. 
Would you be interested in this role?

I would also like to see the likes of Brian, Jon Hebb, Kashidom, Aaron 
and other web devs (you know who you are!) to step in and help with this 
project. I believe with the combined skill level we have we can create a 

Re: [opennic-discuss] OpenNIC discussion about the current state and future...

<snip>

> As I said some time ago. I think the first thing to do is to build a bullit
> proof system, that's good architected and works as we likes. The design
> method that I purposed can probably help us here by. So first there is need
> for voluntiers that have some spare space on their DNS servers. Then there
> is need to build a bullit proof, self containing audit system that alert us
> when things go wrong. So with those two things covered there is space to
> build and intergrate some management system in first run for server
> maintainers, then for TLD maintainers, after that domain registration,
> completed by an user information and administration system. 

We already have a good architecture that works. We also still have our 
  monitoring in place. Nagios is still watching over our systems. At 
present, it needs a bit of work to it. This is my fault, and when I 
get a free moment I will fix Nagios fully.

So in saying that, our architecture, and auditing systems are pretty 
sound, and have been for some time now.

>After that all
> these 'modules' (because they can co esists on the same, shared foundation
> of Programmaticly API's) have to boiled down in an WHOIS information
> reposotory that makes this information uniformly accessable, and if there is
> need for, changeable.
> 

I have already made progress with a whois server. It is currently 
running at 58.6.115.44 and is returning whois information for the geek 
TLD. The only part missing is domain registration and management.

Re: [opennic-discuss] OpenNIC discussion about the current state and future...

brian <at> pongonova.net wrote:
> On Mon, Jun 30, 2008 at 09:54:55PM +0100, Axel Pivot wrote:
>> **Since ICANN and all of it's subsidiary and associated bodies are, like it
>> or not, a major part of that outside world, then they are also part and
>> parcel of the PR Group's remit.  Dialogue of any form, with any of these
>> organisations,  should not be discounted simply because it is felt to be
>> of no value. Think fall of the walls of Jericho but without all the maiming
>> and killing that supposedly went on afterward.
> 
> I see you still haven't done your research, so let me give you a
> hand...

Thanks kindly, but a hand isn't really necessary.

As for your references, well sorry, but I see no point or value in you quoting
any of them.  We are talking about history yet to be written, not history already
cast in stone. Things change, people change, opinions change and *can be* changed.

> This is by no means intended to be complete or unbiased collection of
> factoids.  I leave that exercise to the reader :)

There are multitudinous references and opinion spread all over the internet, from
http://icannwatch.org to the ICANN forums themselves: http://forum.icann.org ( inc
one of the original ones, http://forum.icann.org/uniqueroot ).  But so what?  If you
wish to be bit of an obsessive factoid collector and historian on all that is bad
with ICANN and it's past attitude to alt roots, then you go right ahead.  Such data
and attitude will not progress the OpenNIC forward on iota.

> I have put these in chronological order.  Hopefully,
> you'll see that not much has changed with regards to ICANN's stance on

Tim Groeneveld <tim <at> timg.ws>

Subject: Re: [opennic-discuss] OpenNIC discussion about the current state and future...

Re: [opennic-discuss] OpenNIC discussion about the current state and future...

On Tuesday 01 July 2008 7:49:42 pm Julian De Marchi wrote:
> I have already made progress with a whois server. It is currently
> running at 58.6.115.44 and is returning whois information for the geek
> TLD. The only part missing is domain registration and management.

My domain registration system for the .ing TLD is pretty much ready for 
consumption, and I will be formally making a release (0.2) on Friday, along 
with allowing open registrations under the dotING top level domain.

Regards,
  - Tim G

Re: [opennic-discuss] OpenNIC discussion about the current state and future...

Tim Groeneveld wrote:
> On Tuesday 01 July 2008 7:49:42 pm Julian De Marchi wrote:
>> I have already made progress with a whois server. It is currently
>> running at 58.6.115.44 and is returning whois information for the geek
>> TLD. The only part missing is domain registration and management.

Still a tad ropey Julian.  Especially as it still allows this kind of
thing..

<quote>
AN Other is requesting 'this.needs.fixing.Julian.geek' for registration.

  Request Details:

  Registrant Name: AN Other
  Email: chris <at> opennic.org.uk
  Address: 1 Any Road
  Postcode: BG6572
  City: Some City
  State: Where?
  Country: Some Country
  Phone: 0000000
  Abuse Email: nospam <at> nospam.com
  DNS IP 1: 192.168.1.90
  DNS IP 2: 10.0.0.2
  Purpose:
  Whatever I feel like
  Notes:
  G flat, B sharp ..
</unquote>

Re: [opennic-discuss] OpenNIC discussion about the current state and future...

On 1 jul 2008, at 11:49, Julian De Marchi wrote:
> It is currently running at 58.6.115.44 and is returning whois  
> information for the geek TLD. The only part missing is domain  
> registration and management.
Julian, I know. But I'd like to paint a more general picture. Of  
course I know that there is very good progress in the Auditing systems  
etc. I also got a glimpse of a WHOIS server...

So it boiled down to a single missing part: management and  
administration. Let's create an Working Group for this task and define  
and create such system. I'd like to coordinate the whole thing. I was  
thinking about an Administration WG that coordinates and administrates  
OpenNIC information (as in Domain registrations, User information,  
Auditing?, etc.).

I think it's a good position for the Administration WG to sit between  
Architecture, Webmastering, Hostmastering, Auditing. That are, I  
think, the WGs that are involved in Administration and data management.

Regards,
-Anner.
-
To unsubscribe, email majordomo <at> lists.opennicproject.org with the words
"unsubscribe discuss" in the body of the message.

Re: [opennic-discuss] Project - Re-Vamped Glue Website

Re: [opennic-discuss] Project - Re-Vamped Glue Website

> Yes I'd like to accept that role. Let's revamp the glue site!

Thank you Anner.

> To answer your questions about Qcodo/SpidioBase. This framework is a 
> foundation to develop web apps of. It contains already written and 
> working code blocks for different tasks. As you may have seen. I'm 
> (very) expanding the core Qcodo framework to make it more suitable as a 
> foundation to start from. So it take even less time to create an 
> proof-of-concept and finally an production web app.

Thank you for the explanation.

> I've read a little bit of the idea, but I'm currently quite a time 
> involved at OpenNIC to guess some of the needs ;). I want to take some 
> time to over think some of the stuff and publish a first proposal, is 
> that alright? 

Thats fine. It is important that we document everything we do on the 
wiki. So on the project page, anything you write should be published 
there. This also goes for ideas. We need to start communicating as 
much we can via the wiki. 

	-http://wiki.opennic.glue/PrivateWebsite

> To help me with that, what is currently the policy for 
> registration and hosting of TLDs? 

I hope this page helps.

	- http://wiki.opennic.glue/CreatingNewTLDs

> Do we want to
> delegate the domain registration an sich to the TLD maintainers,
> delegate the domain registration with some sort of meta-portal 
> functionality on opennic.glue (or an other domain in the glue TLD space),
> take an centralized location for domain registration?

Domain registration does not come into play with the new glue site as 
of yet. We will want this in the future, but our TLDs are not ready. 
We first need solid TLD management software in place with APIs 
enabling the remote registration of domain names. The newly created 
TLD .ing will be a perfect example of such software when it comes 
online. So for now, we do not need to focus on domain registrations 
from the glue site.

> I think, to reflect the OpenNIC philosophies, we must create some sort 
> of meta portal (with an shadow of all TLD domain registration data) 
> which has the functionality to push of the registration to the TLD 
> registrations system by some sort of web service. With this concept you 
> can let stand the TLD on their own but make them also part of the 
> project and it's infrastructures.

I hope my comments above also answer this question.

> What are the current numbers of registered domains?

This wiki page will help answer that question.

	- http://wiki.opennic.glue/SponsoredTLDs

It is needing some attention at the moment, and I have not got round 
to having a look at it yet. But it will give you some numbers.

> For development purposes, hereby I purpose an restricted development TLD 
> called .dev and is maintained as an core TLD like the glue TLD. It 
> contains a very basic reflection of the real world OpenNIC project, such 
> a handful of domains etc. Really a development sandbox.

Could we not use *.dev.glue, and save the need of managing another 
TLD? A subdomain other then opennic I think should be possible. Would 
any one disagree?

--Julian
-
To unsubscribe, email majordomo <at> lists.opennicproject.org with the words
"unsubscribe discuss" in the body of the message.

[opennic-discuss] pre public site

Hi there :)
The site i've setup is http://peregrina.byethost7.com/ where you can edit the contents yourselves. If
you don't like something, anything, just edit the page (in the drop-down menu in the center above the "onic
logo" , click "edit" and "go". I assume you all know html :P ). You can even create pages by looking the URL,
its /edit?lang=english&what=wtf    if you want to create a new page called "wtf" in the english language :)
Thanks for reading.

--

-- 
Be Yourself  <at>  mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

-
To unsubscribe, email majordomo <at> lists.opennicproject.org with the words
"unsubscribe discuss" in the body of the message.

[opennic-discuss] Public site replacement

Currently active in http://help.opennicproject.org/
I think this should replace the public site, don't you?
Any thoughts, ideas?

--

-- 
Be Yourself  <at>  mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

-
To unsubscribe, email majordomo <at> lists.opennicproject.org with the words
"unsubscribe discuss" in the body of the message.