tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki

launch allmydata.org #1

New Issue
Closed
opened 2007-04-22 22:24:04 +00:00 by warner · 8 comments
warner commented 2007-04-22 22:24:04 +00:00
Copy Link

Things still left to do before launch:

  • fix zfec to install under 2.4 (the relative ..util in cmdline.zfec breaks byte-compilation)
  • set up public testnet
  • upgrade tahoebs1,tahoecs1 to latest build
  • add links to wiki
  • mirror darcs repo to org
  • currently done hourly, should change to be on-demand
  • proxy buildbot waterfall to dev
  • disable force-build on the proxied view
  • obsfuscate email addresses on the waterfall
  • mirror figleaf coverage data to org on each build
  • split tahoe APT repo out from the rest
  • mirror it to org on each build
  • make figleaf coverage munin graph visible
  • move tahoe docs from dev to org
  • decide on use of SSL
  • mailing list
  • trac-darcs plugin, trac code browser
  • decide about obsfuscating email addresses
  • hack trac-darcs to munge addresses on the way in, that should take care of leakage through trac

Lower priority items:

  • fix python2.5-vs-2.4 API warning in neo_cgi, neo_cs stuff
  • get support debs into repository (foolscap?)
  • get support tarballs into repository
  • update license in tahoe .debs to reflect GPLness
  • XMLRPC plugin for trac, to enable easier wiki editing (from emacs)
Things still left to do before launch: * ~~fix zfec to install under 2.4 (the relative ..util in cmdline.zfec breaks byte-compilation)~~ * ~~set up public testnet~~ * ~~upgrade tahoebs1,tahoecs1 to latest build~~ * ~~add links to wiki~~ * ~~mirror darcs repo to org~~ * currently done hourly, should change to be on-demand * ~~proxy buildbot waterfall to dev~~ * ~~disable force-build on the proxied view~~ * ~~obsfuscate email addresses on the waterfall~~ * ~~mirror figleaf coverage data to org on each build~~ * ~~split tahoe APT repo out from the rest~~ * ~~mirror it to org on each build~~ * ~~make figleaf coverage munin graph visible~~ * ~~move tahoe docs from dev to org~~ * decide on use of SSL * ~~mailing list~~ * ~~trac-darcs plugin, trac code browser~~ * ~~decide about obsfuscating email addresses~~ * ~~hack trac-darcs to munge addresses on the way in, that should take care of leakage through trac~~ Lower priority items: * fix python2.5-vs-2.4 API warning in neo_cgi, neo_cs stuff * get support debs into repository (foolscap?) * ~~get support tarballs into repository~~ * ~~update license in tahoe .debs to reflect GPLness~~ * XMLRPC plugin for trac, to enable easier wiki editing (from emacs)
warner added the
major
task
 labels 2007-04-22 22:24:04 +00:00
warner commented 2007-04-23 00:27:46 +00:00
Author
Copy Link

.debs, figleaf html are now in place

.debs, figleaf html are now in place
warner commented 2007-04-23 19:18:35 +00:00
Author
Copy Link

hiding email addresses by hacking tailor and buildbot

hiding email addresses by hacking tailor and buildbot
warner commented 2007-04-24 00:42:19 +00:00
Author
Copy Link

apt repository is working

apt repository is working
warner commented 2007-04-24 01:03:22 +00:00
Author
Copy Link

hacked buildbot to obsfuscate email addresses on the waterfall and rendered Changes. There are still a few that show up in the darcs update logs, but I think I'm not going to worry about those.

hacked buildbot to obsfuscate email addresses on the waterfall and rendered Changes. There are still a few that show up in the darcs update logs, but I think I'm not going to worry about those.
warner commented 2007-04-26 01:43:58 +00:00
Author
Copy Link

it'd be nice to have a public testnet too

it'd be nice to have a public testnet too
zooko commented 2007-04-26 17:17:46 +00:00
Copy Link

fix zfec to install under 2.4 (the relative ..util in cmdline.zfec breaks byte-compilation)

I created ticket #4 to track this one specifically. (Partially just to explore ticket creation, etc...)

> fix zfec to install under 2.4 (the relative ..util in cmdline.zfec breaks byte-compilation) I created ticket #4 to track this one specifically. (Partially just to explore ticket creation, etc...)
warner commented 2007-04-27 02:41:00 +00:00
Author
Copy Link

upgraded the public testnet. there are some foolscap issues there, but I think I've patched them well enough to hold until the next foolscap release

upgraded the public testnet. there are some foolscap issues there, but I think I've patched them well enough to hold until the next foolscap release
warner added the
website
 label 2007-04-28 19:16:23 +00:00
warner commented 2007-05-03 17:30:46 +00:00
Author
Copy Link

We've launched. I moved the remaining low-priority items to #30

We've launched. I moved the remaining low-priority items to #30
warner added the
fixed
 label 2007-05-03 17:30:46 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?