0000684: Endian Firewall SVN Repository

(0001002)
nicoprenzel (reporter)
2008-04-16 14:31

There are sources, but they are dated to 26 Jun 2007 and Endian EFW 2.1.1!

I support the request, issued by the previous reporter 'bet0x' to publish the EFW to a SVN repository.

The "slow" development process could be increased dramatically, if you'll consider that request. With some defined regulations you could also assure that the development process would be on the right path.

Please think of it and do it!

Greeting

NicoP.

(0001003)
bet0x (reporter)
2008-04-16 14:42

We will see what they answer. I get negative answers the last time =/ (when i saw aobut the SVN they close it).

(0001006)
bet0x (reporter)
2008-04-17 12:00

as we see, there is no answer of Endian staff.

(0001007)
raphael (administrator)
2008-04-17 12:48

We'll release the sources together with the final 2.2 release in May. SVN will be opened ASAP, it's on our Todo list, but as you probably could guess it's very long...
It's not right that there are no sources, because most of the code is in python/perl scripts that can be modified without any re-compilation.

If you would like to contribute then help us finding/fixing bugs :)

(0001019)
bet0x (reporter)
2008-04-22 22:27
edited on: 2008-04-22 22:29

We dont want to contribute "testing" a little % of the EFW community are coders, like me, we want develop, access to sources and more.

Your way is a closed source way, you call it open because marketing and no more.

Choose one side, dont stay on the middle. That is why people create forks of projects, when the creators do this things, just promises and no more. I want to see more than words because i wait for that SVN two years, if you check the mailing list you will see my email there ;).

If you want contributions do your real part.

(0001020)
raphael (administrator)
2008-04-23 10:23

It doesn't make much sense to just open SVN and say "here it is", because everyone would keep asking "how do i build that", "ho do i change that", etc.

Right now we're busy finishing 2.2, SVN will be opened after the release (Q3/2008).

(0001026)
bet0x (reporter)
2008-04-23 19:03

Perfect, but as all know, SVN is not just for fun, is for track & develop, so there u got the answer for those's who can ask about "how to that" ;) filter them.

finishing 2.2? not wasn't announced on the first page of Endian website?

(0001165)
cmateski (reporter)
2008-05-14 15:13

I totally agree that SVN should be implemented. The "Endian Firewall Community ISO" page http://www.endian.com/en/community/download/updates-and-source/ [^] really should show the timeline for bringing SVN online.

SVN will enable more developers to get involved and hopefully speed up the dev cycle.

On a similar note, why aren't the SOURCE files for 2.1.2 available?

(0001284)
bet0x (reporter)
2008-06-03 21:19

We still waiting.

(0001295)
bet0x (reporter)
2008-06-09 14:35

And we still waiting and waiting!

(0001296)
Devroush (reporter)
2008-06-09 22:30
edited on: 2008-06-09 22:32

"Right now we're busy finishing 2.2, SVN will be opened after the release (Q3/2008)."

I don't think it can be much clearer than this.. I agree that svn would really help this project but let's just stay patient :).

(oh and I'm a big fan of Trac if svn gets set up)

(0001325)
clubbing80s (reporter)
2008-06-18 11:07

I'm with bet0x on this one and have been complaining on the lists as well would rather work on the project with the guys than have to goto the trouble of forking the project.
At the moment the community is just used for testing. and then we have to sit on our hands until the next release because no updates have been released for current releases.
Yes a fair part of efw is in scripted languages. but that doesn't help when you want to add functionality of fix a binary that's been installed in rpm format, we also need the latest source rpms so we can rebuild and compile new rpms ..
I really like this project and take my hat off to the developers for putting together a grate product but this is not a true open source project.. I wait with baited breath for the release of 2.2 with the source..

(0001379)
steven (reporter)
2008-06-27 09:51

I also look forward to the creation of an SVN and more feedback from the Endian Team

(0001623)
bet0x (reporter)
2008-09-16 10:04

We still waiting.

(0001655)
DarkServant (reporter)
2008-10-06 19:24

We still waiting.

(0001656)
steven (reporter)
2008-10-06 23:08

anyone from Endian care to reply?

(0001662)
chris (manager)
2008-10-07 19:11

Hi,

let's discuss this on the mailing lists.

http://sourceforge.net/mail/?group_id=132104 [^]

I'm closing this. See you over there.

Bye,
Chris.

(0002414)
bet0x (reporter)
2009-05-27 22:13

We still waiting for this, look the date of my issue and look the date of my reply, 1 year ago. You dont want to open or do anything regarding EFW far as we know.

(0002523)
peter (administrator)
2009-06-09 19:04

closing this, since it has been closed already and is definitively no bug
please leave it closed and write to the mailinglist instead.

Issue History
Date Modified	Username	Field	Change
2008-04-16 13:31	bet0x	New Issue
2008-04-16 14:31	nicoprenzel	Note Added: 0001002
2008-04-16 14:42	bet0x	Note Added: 0001003
2008-04-17 12:00	bet0x	Note Added: 0001006
2008-04-17 12:48	raphael	Note Added: 0001007
2008-04-17 12:48	raphael	Status	new => closed
2008-04-17 12:48	raphael	Resolution	open => no change required
2008-04-22 22:27	bet0x	Status	closed => feedback
2008-04-22 22:27	bet0x	Resolution	no change required => reopened
2008-04-22 22:27	bet0x	Note Added: 0001019
2008-04-22 22:29	bet0x	Note Edited: 0001019
2008-04-23 10:23	raphael	Note Added: 0001020
2008-04-23 10:24	raphael	Summary	Two years of Endian project, and no sources. => Endian Firewall SVN Repository
2008-04-23 10:24	raphael	Description Updated
2008-04-23 10:26	raphael	Severity	minor => feature
2008-04-23 10:27	raphael	Status	feedback => confirmed
2008-04-23 10:27	raphael	Resolution	reopened => open
2008-04-23 19:03	bet0x	Note Added: 0001026
2008-05-14 15:13	cmateski	Note Added: 0001165
2008-06-03 21:19	bet0x	Note Added: 0001284
2008-06-09 14:35	bet0x	Note Added: 0001295
2008-06-09 22:30	Devroush	Note Added: 0001296
2008-06-09 22:31	Devroush	Note Edited: 0001296
2008-06-09 22:31	Devroush	Note Edited: 0001296
2008-06-09 22:32	Devroush	Note Edited: 0001296
2008-06-18 11:07	clubbing80s	Note Added: 0001325
2008-06-27 09:51	steven	Note Added: 0001379
2008-06-30 12:35	yxcv	Issue Monitored: yxcv
2008-07-01 20:01	peter	Target Version	=> 2.3
2008-07-02 19:22	mgabriel	Issue Monitored: mgabriel
2008-07-03 10:17	sgiunchi	Issue Monitored: sgiunchi
2008-09-16 10:04	bet0x	Note Added: 0001623
2008-10-06 19:24	DarkServant	Note Added: 0001655
2008-10-06 23:08	steven	Note Added: 0001656
2008-10-07 19:11	chris	Note Added: 0001662
2008-10-07 19:12	chris	Resolution	open => suspended
2008-10-07 19:13	chris	Status	confirmed => closed
2009-05-27 22:13	bet0x	Note Added: 0002414
2009-05-27 22:13	bet0x	Status	closed => feedback
2009-05-27 22:13	bet0x	Resolution	suspended => reopened
2009-06-09 19:04	peter	Note Added: 0002523
2009-06-09 19:04	peter	Status	feedback => closed
2009-06-09 19:04	peter	Resolution	reopened => suspended

Notes
(0001002) nicoprenzel (reporter) 2008-04-16 14:31	There are sources, but they are dated to 26 Jun 2007 and Endian EFW 2.1.1! I support the request, issued by the previous reporter 'bet0x' to publish the EFW to a SVN repository. The "slow" development process could be increased dramatically, if you'll consider that request. With some defined regulations you could also assure that the development process would be on the right path. Please think of it and do it! Greeting NicoP.

(0001003) bet0x (reporter) 2008-04-16 14:42	We will see what they answer. I get negative answers the last time =/ (when i saw aobut the SVN they close it).

(0001006) bet0x (reporter) 2008-04-17 12:00	as we see, there is no answer of Endian staff.

(0001007) raphael (administrator) 2008-04-17 12:48	We'll release the sources together with the final 2.2 release in May. SVN will be opened ASAP, it's on our Todo list, but as you probably could guess it's very long... It's not right that there are no sources, because most of the code is in python/perl scripts that can be modified without any re-compilation. If you would like to contribute then help us finding/fixing bugs :)

(0001019) bet0x (reporter) 2008-04-22 22:27 edited on: 2008-04-22 22:29	We dont want to contribute "testing" a little % of the EFW community are coders, like me, we want develop, access to sources and more. Your way is a closed source way, you call it open because marketing and no more. Choose one side, dont stay on the middle. That is why people create forks of projects, when the creators do this things, just promises and no more. I want to see more than words because i wait for that SVN two years, if you check the mailing list you will see my email there ;). If you want contributions do your real part.

(0001020) raphael (administrator) 2008-04-23 10:23	It doesn't make much sense to just open SVN and say "here it is", because everyone would keep asking "how do i build that", "ho do i change that", etc. Right now we're busy finishing 2.2, SVN will be opened after the release (Q3/2008).

(0001026) bet0x (reporter) 2008-04-23 19:03	Perfect, but as all know, SVN is not just for fun, is for track & develop, so there u got the answer for those's who can ask about "how to that" ;) filter them. finishing 2.2? not wasn't announced on the first page of Endian website?

(0001165) cmateski (reporter) 2008-05-14 15:13	I totally agree that SVN should be implemented. The "Endian Firewall Community ISO" page http://www.endian.com/en/community/download/updates-and-source/ [^] really should show the timeline for bringing SVN online. SVN will enable more developers to get involved and hopefully speed up the dev cycle. On a similar note, why aren't the SOURCE files for 2.1.2 available?

(0001284) bet0x (reporter) 2008-06-03 21:19	We still waiting.

(0001295) bet0x (reporter) 2008-06-09 14:35	And we still waiting and waiting!

(0001296) Devroush (reporter) 2008-06-09 22:30 edited on: 2008-06-09 22:32	"Right now we're busy finishing 2.2, SVN will be opened after the release (Q3/2008)." I don't think it can be much clearer than this.. I agree that svn would really help this project but let's just stay patient :). (oh and I'm a big fan of Trac if svn gets set up)

(0001325) clubbing80s (reporter) 2008-06-18 11:07	I'm with bet0x on this one and have been complaining on the lists as well would rather work on the project with the guys than have to goto the trouble of forking the project. At the moment the community is just used for testing. and then we have to sit on our hands until the next release because no updates have been released for current releases. Yes a fair part of efw is in scripted languages. but that doesn't help when you want to add functionality of fix a binary that's been installed in rpm format, we also need the latest source rpms so we can rebuild and compile new rpms .. I really like this project and take my hat off to the developers for putting together a grate product but this is not a true open source project.. I wait with baited breath for the release of 2.2 with the source..

(0001379) steven (reporter) 2008-06-27 09:51	I also look forward to the creation of an SVN and more feedback from the Endian Team

(0001623) bet0x (reporter) 2008-09-16 10:04	We still waiting.

(0001655) DarkServant (reporter) 2008-10-06 19:24	We still waiting.

(0001656) steven (reporter) 2008-10-06 23:08	anyone from Endian care to reply?

(0001662) chris (manager) 2008-10-07 19:11	Hi, let's discuss this on the mailing lists. http://sourceforge.net/mail/?group_id=132104 [^] I'm closing this. See you over there. Bye, Chris.

(0002414) bet0x (reporter) 2009-05-27 22:13	We still waiting for this, look the date of my issue and look the date of my reply, 1 year ago. You dont want to open or do anything regarding EFW far as we know.

(0002523) peter (administrator) 2009-06-09 19:04	closing this, since it has been closed already and is definitively no bug please leave it closed and write to the mailinglist instead.

Relationships