gmane.comp.encryption.cryptobox.devel

Re: Moving the project somewhere else

Hartmut Goebel — 2011-08-03T10:19:28

Am 27.07.2011 23:03, schrieb James Crofts:

Nobody else stepped forward to decide, but you did. So your decision is 
the relevant one :-) So if you decided to move the project to Codesion, 
just do it.

Re: Moving the project somewhere else

James Crofts — 2011-07-27T21:03:24

You previously said Sourceforge excludes some countries. Talking to
Codesion sales, I got the impression that they don't block downloads
from anywhere. I wasn't getting a lot of feedback from you guys as to
where you thought we should move the project, and I wanted to get things
moving so we could have a writeable, CAPTCHA-enabled version of Trac.
It's not too late to make a different decision.

Re: Moving the project somewhere else

Hartmut Goebel — 2011-07-26T07:09:13

Hi James,
I did not find "the right one" yet. FreeNAS would be my favirite, but it 
uses FreeBSD, which is only available for x86 but not for ARM.
I really wonder why you are moving to codesion, which requires:

Sourceforge does also support trac and git any you may even put your 
repository somewhere else.

Re: Moving the project somewhere else

James Crofts — 2011-07-25T22:12:25

Lars and/or Henning: I *need* the Trac Backup file produced by the
trac-admin "hotcopy" command. Instructions for how to do this may be
found at
http://trac.edgewall.org/wiki/TracBackup


I've started a trial account with codesion, primarily to keep track of
my own documentation in a Trac wiki. I brought up the topic of a Free
Software account with the saleswoman, and her response is below. Their
requirements seem reasonable. After playing with git-svn some more I
think it's better to stay with SVN for at least another CryptoNAS
release or two.

Hartmut, once you figure out which NAS project you decide to work on, I
hope you'll tell me so I can watch it closely :)

Since no one has expressed any objection, I will be moving Trac over to
codesion.com and signing up on our behalf for a Free Software Account.

----------

Hi James, 

Thank you for your email and information! You may add custom Trac
permissions through our Security tab: Codesion Roles and Permissions
Explained in Detail.
<https://help.codesion.co

Re: Moving the project somewhere else

Hartmut Goebel — 2011-07-24T18:16:30

Am 06.07.2011 09:22, schrieb James Crofts:

After I had some holidays, I made my mind up about CrytptoNAS. In short:
I *may* help bringing CryptoNAS to Debian 5 (squeeze), if I'll have
enough spare time in the next month. But I will not spend too much time.

While I really like the idea of having all my data encrypted (including
the root partition), I'm more demanding for ease of setup and usage. So
another NAS project would server me more -- but none of the once I
checked out lately really fits my needs.

CryptoNAS has the major advantage that it ma be used as an add-on on a
normal Debian system. So if somebody needs encryption and a easy to use
GUI, CyptoNAS is the way to go. But he has to do everything else by his
own :-(.

I thought about enhancing CryptoNAS to serve my needs. But this would
require quite a lot of time. It should be easier to add encryption to
one of the other NAS projects than bringing all the features to CryptoNAS.

So I decided to not spend too much time for CryptoNAS. Esp. since I
st

Re: Moving the project somewhere else

James Crofts — 2011-07-06T07:22:53

I think moving the Trac wiki sooner rather than later would have great
benefits. I'm working on provisioning a VirtualBox virtual machine for
unit testing, and I'd really like to document the setup in a place where
everyone can find it later.

Have you (Hartmut and anybody else listening) had a chance to think
about what we're looking for in a new hosting provider?

--James

Re: Moving the project somewhere else

James Crofts — 2011-06-13T23:21:45

Me neither. I think Trac got switched to read-only as a result of all
the spam.

I'll be doing my own soul-searching as to exactly what role I should
take in the project.

Re: Moving the project somewhere else

Hartmut Goebel — 2011-06-13T20:09:16

Am 13.06.2011 21:13, schrieb James Crofts:
Great to hear, since I have no clue about building Live-CDs.
I have SVN access, but not access to Trak :-(

Re: Moving the project somewhere else

James Crofts — 2011-06-13T19:13:46

I'm willing to continue to build the Live CD/Live USB-HDD images for the
foreseeable future. Doing everything on my own, however, was beyond
frustrating.

Have you gotten Lars/Henning to give you a SVN account?


Hartmut Goebel wrote:

Automated Reply - Email Received

2011-06-12T23:04:28

We received your e-mail on 6/12/11.  Our Customer Call Center is reviewing 
your inquiry and will respond to your correspondence within the next 24 
hours. If your email is received after 5 pm eastern, you will receive a 
response on the following business day. Your Case ID is 1910517.

Please DO NOT reply to this automatic acknowledgement.

Your business is very important to us and we appreciate the opportunity to 
be of service.

Sincerely,

AXA Equitable
**********************************************************************

Confidentiality Note: This message and any attachments 
may contain legally privileged and/or confidential information. 
Any unauthorized disclosure, use or dissemination of this e-mail 
message or its contents, either in whole or in part, is prohibited. 
If you are not the intended recipient of this e-mail message, 
kindly notify the sender and then destroy it.

**********************************************************************

Re: Moving the project somewhere else

Hartmut Goebel — 2011-06-11T18:03:35

Hi James,

It's my fault: I've been busy the last weeks and I'm still not able to 
access Trac. Among others I thought about requirements for a NAS / home 
server and checked alternatives. I'll write it up the next days.

My plan is to write up vision for CryptoNAS the next days (based on my 
very personal requirements). I'm hoping for a lively discussion here on 
the mailinglist. IMHO we first should we have a clear vision, and the 
discuss again where to move the project.

For now IMHO we can live with the current development platform. If the 
project gains momentum again (what I hope), we can still move.

Re: Moving the project somewhere else

James Crofts — 2011-06-04T06:12:50

I haven't heard back from anyone in a few weeks. It's very possible I
was overlooking good hosting options before because (1) I hadn't clearly
identified my requirements as Hartmut asked that I do and (2) I don't
know much about the user interfaces of Sourceforge and other hosts that
use unique project management software.

Now that Hartmut has convinced me to be less picky, do any of you have
any comments? Which hosted project management software of this type have
you used before?


James Crofts wrote:

Re: Moving the project somewhere else

James Crofts — 2011-05-19T22:29:09

Good question. The most important Trac features to me are the Wiki and
an intuitive way to browse the source repository, changesets, "timeline"
for checkins, and diffs. The request tracker is very desirable, but I
can live with it not being integrated with everything else.

Trac seemed like a good choice because it would simplify migrating data
over from systemausfall. I know that the Trac wiki uses different syntax
from Media Wiki.



I think Git's version hashing may help to inspire confidence in
CryptoNAS's integrity. Does Mercurial resist tampering in the same way
(e.g. changes cannot be made to the repository without it being obvious,
even if performed by "root")?

Re: Moving the project somewhere else

Hartmut Goebel — 2011-05-19T21:41:53

Am 18.05.2011 23:04, schrieb James Crofts:

Okay, I should have written: please review the requirements there. Sorry
for not being clear enough.

So please state *your* requirements. If you are asking about "Trak",
which feature of Trak are you urging for? The wiki, the request tracker,
the roadmap, the tight integration of all this together and with the
source repository, or you-name-it?

AFAIK: If(!) check-ins are marked with e.g. a proper Trak-issue number,
Trak can automatically connect the issue with the checkin. So if the
source repo is on the same machine as Trak or can talk to Trak (as
github seams to support it), one may get some advantages. But do we need it?

BTW: You are talking about git all the time. I personally prefer
mercurial, but github offers far more features than bitbucket. So git
seams to be the better choice here :-(

Re: Moving the project somewhere else

James Crofts — 2011-05-18T21:04:00

I've read this, I just think there may be options we're overlooking.
See, for example:
http://codesion.com/products/open-source.html

I also talked with a rep from webfaction.com. They have given free
hosting to FOSS projects in the past, and they may still do so if
management likes our project:
----------
Sean F: Our management team can review your project and if they decide
to support it, then perhaps we can work something out. Please use our
contact form at http://www.webfaction.com/contact/ to let us know the
details of your project, and I'll pass that info along to our management
team.
----------

I've been looking at several of the hosts at
https://git.wiki.kernel.org/index.php/GitHosting, too.

I read your ticket #19444 on Sourceforge. I don't know much about Trac's
"under the hood" operation. Is there any advantage to having the same
host for Git and Trac? It sounds as though the two systems can talk
gracefully over the Internet with the right plugins/hooks, but for
example, would they be talking ove

Re: Moving the project somewhere else

Hartmut Goebel — 2011-05-18T08:59:46

Am 17.05.2011 22:21, schrieb James Crofts:
Please have a look at my shortlist at 
<https://systemausfall.org/mail-archive/?0::408>.

Berlios offers a wiki, but AFAIK not Trac.

SF offers Trac, but source should live somewhere else since SF excludes 
some countries. So one option could be SF+github. github offers some 
service hook for pushing infos to Trak, but I do not know whether SF as 
installed the required plugin (see 
<https://sourceforge.net/apps/trac/sourceforge/ticket/19444>).

Re: What should find_blockdevices() return?

Hartmut Goebel — 2011-05-18T08:08:09

Am 17.05.2011 23:26, schrieb James Crofts:

Thanks for this offer, but I will not need it. In case 
of find_blockdevices() there is no doc string, thus no doc.

Re: What should find_blockdevices() return?

James Crofts — 2011-05-17T21:26:27

The truth is, I never got around to hunting this down. We used to have
pydoc-generated hyperlinked documentation, but the permissions on that
part of the website mysteriously changed so that it is no longer
accessible. I can send you a tarball of the docs if you like in case it
may help you sorting this out.

Re: Moving the project somewhere else

James Crofts — 2011-05-17T20:21:33

Hartmut, try adding:

deb http://snapshots.cryptonas.org/debian/ unstable free
deb-src http://snapshots.cryptonas.org/debian/ unstable free

to /etc/apt/sources.list. This should allow you to download the
cryptobox-server source code using Debian's package tools. I may not
keep this online forever, particularly if it gets a lot of traffic. Once
we figure out where we're moving the project, it can be hosted by the
web space provided by the new service. If you wish, you can copy it as a
starting point for your own custom repository, since it's fairly small
in size.


If we used BerlIOS, would we continue to be able to use Trac? Should we
think about commercial services that give free accounts to Free Software
projects?

Re: Moving the project somewhere else

Hartmut Goebel — 2011-05-13T14:10:54

Hi Henning,

thanks for you feedback.

Am 13.05.2011 15:41, schrieb Henning:
We'll see :-) CryptoNAS is well linked, the  website is well designed 
and the look and feel is fine. So hopefully we could attract more users 
and a new maintainer.

My idea is just to unburden you from the admin tasks (and remove the 
bottleneck). I would appreciate if you would "install" the project at 
the new place, so you are still the chiefs. And if you could continue 
contributing :-)

(I've set up some development platforms earlier for my mininal use and 
was happy when I could move them away and do no longer care about 
maintaining the system. I can imagine it's the same at your side/site.)

Keeping the webspace at systemausfall has one big disadvantage: It still 
needs somebody to maintain users for svn-access, etc. So this will still 
be a burden for you.

This was what I hoped for. (I hope you mean "lend" (German: leihen) 
instead of "rent" (German: vermieten) :-)


Except for new check-ins, which would require write-ac

Re: Moving the project somewhere else

Henning — 2011-05-13T13:41:22

Hi,

moving to another hosting location would be perfect as it removes Lars
and me as administrative bottleneck. The question is, who is able and
willing to care for the project in the next years?


Just my five cents: berlios


Sounds fine. The mailinglist and translation software is used by other
projects, too. So we will continue to maintain it, same with the
webspace.

We also rent the domain names cryptobox.org and cryptonas.org and point
it to whereever the cryptonas homepage is. If there is establishing a
new group of developers we are willing to give it away.

Btw. we don't plan to shut down the svn. So there's no need to hurry.

May the source be with you :)
Henning