emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Tim Cross <theophilusx@gmail.com>, Bastien <bzg@gnu.org>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: More Worg build workflow
Date: Wed, 15 Jun 2022 13:54:19 +0800	[thread overview]
Message-ID: <87letyv5dg.fsf@localhost> (raw)
In-Reply-To: <87y1xzieb0.fsf@gmail.com>

Tim Cross <theophilusx@gmail.com> writes:

> Based on only a few hours going through worg and Org mode's support for
> generating static web content, there are 3 very broad goals I would like
> to achieve 
> 1. Improve worg's presentation layer to 
> ...
> 2. Make it easier for users to contribute new content, updates for
>    existing content or provide feedback  
> 3. Improve the build and deployment workflow. 
> ...

Sounds good.

> What I'm thinking and wanted feedback on is
> 1. Update the build process to be based on org publish by defining an
>    org-publish-project-alist variable.

This does make sense.

> 2. Moving as many 'global' and/or static settings to be managed within
>    the org-publish-project-alist properties and removing them from each
>    individual org file.

Also makes sense.

> Finally, as this is likely to be a sizeable piece of work, can anyone
> tell me if the FSF copyright assignment process comes into play? I know
> this is the case with org changes, but I'm hoping it isn't with worg as
> I have other constraints which prevent me from signing such an
> agreement. 

No, AFAIK. WORG is supposed to be more lax licence-wise.

I am CCing Bastien in case if there are any cavears I am not aware


      reply	other threads:[~2022-06-15  5:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 12:17 More Worg build workflow Tim Cross
2022-06-15  5:54 ` Ihor Radchenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87letyv5dg.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).