[ previous ] [ next ] [ threads ]
 
 From:  Kendrick Vargas <ken at hudat dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall-dev] m0n0AP - m0n0Cored Project Launch
 Date:  Sat, 04 Aug 2007 03:30:57 -0400
schiz0wall ? Split personalities (OS's), same body, got a 0 and a wall in
there too for good measure. :-)
			-peace

Chris Dickens wrote:
> The name of the project should be logical rather than physical.  Users
> will not understand m0n0core is a firewall.  Maybe you can find some
> variation on the current product's name which still sounds like a
> firewall but still not be mistaken for the existing FreeBSD based
> system.
> 
> Users don't care if it has a fancy new core architecture, they want to
> see something like "m0n0wall II" or "m0n0wall extreme" - something
> creative. :-)
> 
> If you want to give it an internal pet name, I suppose you could start
> using gemstones or something like that - and then you really haven't a
> clue what it is just from the internal name.  Afterall, who'd have
> guessed Longhorn is an operating system without someone telling you? :-)
> 
> --Chris
> 
> -----Original Message-----
> From: Junior Gillespie [mailto:junior dot gillespie at gmail dot com] 
> Sent: Friday, August 03, 2007 7:08 PM
> To: Jayden Phillips; m0n0wall dash dev at lists dot m0n0 dot ch; m0n0wall at lists dot m0n0 dot ch
> Subject: Re: [m0n0wall-dev] m0n0AP - m0n0Cored Project Launch
> 
> On 8/3/07, Jayden Phillips <trainguy77 at shaw dot ca> wrote:
>> Well why not keep the name m0n0wall. As its still going to be the
>> same thing just with more modular design am i correct?
> 
> 
>  That's a good question! We could probably keep a partial "m0n0" in the
> project name, and being known as m0n0Cored isn't so bad. But the reason
> why
> were not m0n0wall is because this is a new design/architecture, and
> doesn't
> fall in line with the current m0n0wall. I've talked with Manuel, and
> he's
> thumbs up with the idea of furthering this project, and hopefully being
> able
> to replace m0n0wall one day. Therefore, this is not m0n0wall, but a
> venture
> into what could be.
> 
> I'm okay with m0n0Core or m0n0Cored, but we need to differentiate
> ourselves
> from m0n0wall, as a m0n0wall derived project with intentions of being
> the
> "NEW" m0n0wall. Also, were deviating from the original FreeBSD OS, and
> looking at a multi-OS solution that is BSD and Linux based.
> 
> 
> I think we
>> need to be sure to get a team going with different people having
>> different responsibilities or the same thing will happen where its
>> very few people running the ship they did a great job but we don't
>> want to burn them out.
> 
> 
> I agree, and thats why were going to adhere to an Organizational Chart
> with
> specific duties.
> 
> 
> I am willing to setup the forum once its
>> installed on a forum. However, I am not any good at web design, so
>> did we want to redesign the entire page? and why? I am not really a
>> developer but i am very technically minded so i am willing to help
>> with user guides forums whatever else needs being done. By the way i
>> am leaving tommorow for 2 weeks so if your wondering why i don't
>> respond thats why.
>>
>> Jayden
>>
>> I think we need our own web presence, with our own intentions and
> goals
> and eventually one day merge back into m0n0wall once we've developed a
> stable solution.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash dev dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash dev dash help at lists dot m0n0 dot ch
>