I'm closing this as it was about defining the naming convention and we have done so. I'm going to file a task about documenting it as part of the data model documentation.

as per discussion, we'd rather keep them self-contained than gain something out of code deduplication

In T1265#23549, @douardda wrote:

yes I'm aware of this logic in the makefile. Not sure yet what's the best to do with this. Move it up in swh-development?

My point was just that you didn't list here the entries that you think have to be updated, so it wasn't actionable.
It would be great if you can update the task description with all the entries that you think deserve an update (even if you've doubts about them).

potentially useful related tooling: http://carsonip.me/posts/debugging-memory-usage-python-tracemalloc/

(BTW, it's incredible how many websites out there are plagued by this
very same issue…)

Can you clarify the scope of this task?

No objections here either.

Oh, yeah, that makes sense. We're doing some refactoring work on
swh-storage these days, so if you did part of the DB setup back then and
part now, weird things might have happened :-)

Thanks for the update, looks even greater now :-)

That is awesome, thanks a lot!

I didn't think of this in relation to T1257, but it's indeed a very valid point.
For consistency we should certainly have HEAD in svn snapshots too.

AOL !

I see the problem in your screenshots, but right now I cannot find any instance of it in the docs deployed at docs.s.o.
Please let me know if/when you find one.
Also, next time you can reproduce it locally it would be great if you can paste somewhere the full log of your sphinx build.

• the default branch for snapshots is defined to be HEAD.
  • if the concept of HEAD exists with the same name in the upstream VCS (f.e. git, svn), this branch should be a literal pointer to the corresponding archived object
  • if the concept of HEAD doesn't exist with the same name in the upstream VCS (f.e. mercurial), this branch should be an alias pointing at the default branch, named using the upstream VCS context (f.e. in the mercurial case, that would be an alias for the tip of the default branch)
  • if the concept of a default branch/version doesn't exist in the upstream VCS, no HEAD branch should exist in the snapshot

Thanks for this bug report!

here's a git repo i've just built for you:

$ git br
* master
  not-a-branch
$ git show-ref not-a-branch
72955907aa477d43dc1c03ee6f5a13c2c49534bd refs/heads/not-a-branch
$ git cat-file -p 72955907aa477d43dc1c03ee6f5a13c2c49534bd
040000 tree 8535775197eeced6f90e9116618c61472ebccb9f	foo

I still think my answer applies, no?

I'm not sure I understand your question (or the purpose of this task). Can you elaborate?

closing as wontfix as the whole website in spanish needs an update in fact...

only minor issues for me, looks good otherwise

nice!

closing to match T337 status

we no longer use a puppet module for phabricator

agreed, they should be removed (I've updated the task title accordingly)

The identification part of this task has been done with documenting/implementing our PIDs, the rest is more suited for the software citation work on which @moranegg is actively working.

task death by a thousand cuts

@olasd @ardumont can this be closed now? if yes, please do; if not, please add subtask(s) about what needs to be done to complete this

this is now T1117

this has been done in bc30e8bc60ac3a310f91a15b5692e6b9bc6a30a3

this is now done (YAY :-)), closing the task to reflect current status

not a blocker for integrating this (assuming tox isn't run automatically by pybuild), but fwiw pifpaf isn't in debian yet, there's an RFP though