sup

A curses threads-with-tags style email client

sup-website.git

git clone https://supmua.dev/git/sup-website/

community/pipermail-archives/sup-talk/2013-02.txt (4734B) - raw

      1 From eg@gaute.vetsj.com  Fri Feb  1 09:54:02 2013
      2 From: eg@gaute.vetsj.com (Gaute Hope)
      3 Date: Fri, 01 Feb 2013 10:54:02 +0100
      4 Subject: [sup-talk] replacement sup wiki
      5 In-Reply-To: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
      6 References: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
      7 Message-ID: <510B90BA.30007@gaute.vetsj.com>
      8 
      9 On 13. jan. 2013 16:22, Hamish D wrote:
     10 > Hello
     11 > 
     12 > I've set up a wiki we can use as a replacement for the old unloved
     13 > wiki - http://foobacca.co.uk/sup/
     14 > 
     15 > Unfortunately, most of the old wiki appears to be lost. The wiki
     16 > software (usemod) only appears to keep the last 10 revisions of each
     17 > page. But most pages have been vandalised far more than that, and so
     18 > the content appears lost. I have checked the wayback machine but it
     19 > doesn't have anything from the wiki. I also note that the wiki is
     20 > covered by a Disallow line in the robots.txt - not sure how long
     21 > that's been there.
     22 > 
     23 > Anyway, please feel free to go and recreate the lost pages, or add new
     24 > content. The new wiki is ikiwiki, which is based on git, so all
     25 > history will remain available. At some point the spammers will start
     26 > hitting it, at which point I'll disable registration, but try
     27 > publishing an account on the front page and see if that foxes the
     28 > spammers. We'll see.
     29 > 
     30 > Hamish
     31 
     32 Sup,
     33 
     34 I just tried to edit an page and got an Internal Server Error. I think
     35 we should make the decision as soon as possible about where to keep the
     36 wiki to avoid the extra work and de-motivating/confusing moving/re-creation.
     37 
     38 Then direct people to the wiki from the README and either remove the
     39 WIKI tab on github or use it.
     40 
     41 Great work on setting up a new wiki, but I think it is even better to
     42 keep it all in one place so I vote for using the github wiki and to set
     43 up a sup/heliotrope site there when the time is ripe. What do you think?
     44 
     45 By the way.. at the moment I am the only public member of the github
     46 organization, is that by design.. ? And you could also make me an owner
     47 (as you previously mentioned) if that gives me the possibility to manage
     48 more of those things!
     49 
     50 Regards, Gaute
     51 
     52 From dmishd@gmail.com  Sun Feb  3 19:10:12 2013
     53 From: dmishd@gmail.com (Hamish D)
     54 Date: Sun, 3 Feb 2013 19:10:12 +0000
     55 Subject: [sup-talk] replacement sup wiki
     56 In-Reply-To: <510B90BA.30007@gaute.vetsj.com>
     57 References: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
     58 	<510B90BA.30007@gaute.vetsj.com>
     59 Message-ID: <CAOxvSbcpfxPrQSsMkxKqF9PFbLV8GtZvNfSKf09OfAbGaxwujw@mail.gmail.com>
     60 
     61 >> I've set up a wiki we can use as a replacement for the old unloved
     62 >> wiki - http://foobacca.co.uk/sup/
     63 >
     64 > I just tried to edit an page and got an Internal Server Error.
     65 
     66 Oops - I've been moving the server and hadn't tested that - fixed now.
     67 
     68 > Great work on setting up a new wiki, but I think it is even better to
     69 > keep it all in one place so I vote for using the github wiki and to set
     70 > up a sup/heliotrope site there when the time is ripe. What do you think?
     71 
     72 Just re-checked and anyone with a github account can edit the wiki
     73 through the front end, which was my main concern. So given using the
     74 github wiki does mean everything is in one place I would now lean
     75 towards the github wiki as the way to go.  I have pushed my wiki
     76 contents to the github wiki to try it out and seems fine:
     77 
     78 https://github.com/sup-heliotrope/sup/wiki
     79 
     80 Matthieu - do you still have a strong preference for ikiwiki?
     81 
     82 > By the way.. at the moment I am the only public member of the github
     83 > organization, is that by design.. ? And you could also make me an owner
     84 > (as you previously mentioned) if that gives me the possibility to manage
     85 > more of those things!
     86 
     87 I've made you an owner and made myself public - the public/private
     88 thing wasn't deliberate, just an accident of how people were added I
     89 think.
     90 
     91 Hamish
     92 
     93 From matthieu.rakotojaona@gmail.com  Mon Feb  4 13:35:52 2013
     94 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
     95 Date: Mon, 4 Feb 2013 14:35:52 +0100
     96 Subject: [sup-talk] replacement sup wiki
     97 In-Reply-To: <CAOxvSbcpfxPrQSsMkxKqF9PFbLV8GtZvNfSKf09OfAbGaxwujw@mail.gmail.com>
     98 References: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
     99 	<510B90BA.30007@gaute.vetsj.com>
    100 	<CAOxvSbcpfxPrQSsMkxKqF9PFbLV8GtZvNfSKf09OfAbGaxwujw@mail.gmail.com>
    101 Message-ID: <CAMiZLn354GOy+PiWjemDvEgQ9v18y5Kp1WQH99G_RxuiqAL46g@mail.gmail.com>
    102 
    103 On Sun, Feb 3, 2013 at 8:10 PM, Hamish D <dmishd at gmail.com> wrote:
    104 > Matthieu - do you still have a strong preference for ikiwiki?
    105 
    106 I've been convinced : centralizing all the resources is the best move
    107 at the moment. My only complaint was about the lack of a search
    108 engine. Let's hope it won't be that bad.
    109 
    110 --
    111 Matthieu RAKOTOJAONA
    112