Apache Allura™ / Tickets / #7926 Set up 'pelican' for publishing our website

Dave Brondsema - 2015-07-13

labels: --> sf-current, sf-4
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2015-07-14

labels: sf-current, sf-4 --> sf-current, sf-4, 42cc

status: open --> in-progress

assigned_to: Igor Bondarenko
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2015-07-17

Closed #822.

All code in the svn repo. See README for some instructions.

I think it would be cool to set up a git repo for allura-site. We need to meet these criteria:

neet to have a repo in https://git-wip-us.apache.org somewhere (seems like it can be a part of Allura repo even, but I'm not sure we want that)

site should be in branch "asf-site"

file a JIRA ticket with infrastructure to setup git based workflow

Can we add a repo to git-wip-us.apache.org somehow? I didn't find any docs on it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Dave Brondsema - 2015-07-17
  
  We can't add a repo ourselves, we'd have to ask ASF Infra to do so (a JIRA ticket in their system). We could do an "asf-site" branch in our current repo, seems like that would work ok. But is a little bit weird to me to have completely separate things in the same repo just using different branches. I do see many projects at https://git-wip-us.apache.org/repos/asf have repos named PROJECT-site or -website or -www so requesting a repo in that pattern seems appropriate to me.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Heith Seewald - 2015-07-17
    
    Did we make a ticket for this?
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Dave Brondsema - 2015-07-17
      
      I haven't. Sounds like we're in agreement that a separate repo (e.g. "allura-site") would be best, so if someone wants to ticket the request, go for it.
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - Heith Seewald - 2015-07-17
        
        I just made a ticket for a new repo called "allura-site" that initially imports from our svn repo.
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        Heith Seewald - 2015-07-17
        
        The new repo has been created:
        
        git clone https://git-wip-us.apache.org/repos/asf/allura-site
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        Dave Brondsema - 2015-07-21
        
        Created https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-10032 to use it for publishing our website.
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        Dave Brondsema - 2015-07-24
        
        We're all switched over now. https://git-wip-us.apache.org/repos/asf?p=allura-site.git;a=shortlog;h=refs/heads/asf-site
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2015-07-17

status: in-progress --> review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2015-07-17

For reviewing this, I started glancing at http://svn.apache.org/viewvc?view=revision&revision=1691521 and http://svn.apache.org/viewvc?view=revision&revision=1691559 There's a lot of files so can you point me at the ones that are "interesting". I mean things that aren't standard pelican files and aren't existing from our site already. So like pelicanconf.py and jinja parts of base.html and index.html. Anything else?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Igor Bondarenko - 2015-07-17
  
  That's pretty much all. + README.md. The future blog posts/pages will go into content/ directory. Now it only contains favicon.ico, .htaccess and robots.txt, but those are the same as in previous revisions.
  
  Everything in the root directory except of readme and _src is generated (or copied from _src) by pelican (make html)
  
  Last edit: Igor Bondarenko 2015-07-17
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2015-07-17

status: review --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2015-07-17

Sweet, looks good and works well for me. We'll have to start writing some content soon!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2015-07-27

labels: sf-current, sf-4, 42cc --> sf-4, 42cc
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2015-08-10

Milestone: unreleased --> v1.3.1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Apache Allura™

Forge software for hosting software projects

Milestone

Searches

Help

#7926 Set up 'pelican' for publishing our website

Discussion