No place for 2016 yet.

[hendrikboom3]

I'm the municipal liaison for nanowrimo in Montreal, and I'd really like to try my hand at text generation.
That's utterly not what nanowrimo is for, so in November is seemed inappropriate to do nanogenmo instead. I'm supposed to set an example, after all.

Anyway, I'd like to start on a generated novel soon, rather than wait until November, and I'd like a place to show it off in progress where others might actually see what I'm doing and chip in with advice. Should I start nanogenmo 2016 early? Should I do it on 2015? in case this issue might be the place.

Or should I buck convention and do it in November anyway? That might not be taken well by nanowrimo headquarters. MLs should live to a higher standard than ordinary writers.

I have no idea what the story is going to be, but I plan to start with data structures for describing whatever kinds of things I might need, and making sentences based on them.

It would be fun to have a map. But that's probably too ambitious.

[hugovk]

Yes! Do one now! Or maybe: June. (We could call it NaJuGenMo.)

Do it here! There's already people watching this repo.

Whether it's an "early 2016" or a "late 2015", who cares?!

Maybe you'll want to do another one in November too! There's nothing really to stop you doing both a NaNoGenMo and NaNoWriMo, except for time. Yeah, the time thing is probably the main obstacle. Then again, there could be some really interesting overlaps in doing a NaNoWriMo-NaNoGenMo mashup: write code to write parts of a 50k novel, with a human writer/editor use it as a prompt, to fill in the gaps, rewrite things and make them more coherent or interesting.

Anyway, back to now. Maps are fun, see these from 2015 for ideas: #156 #166

[ikarth]

Emily Short and Darius Kazemi both did some interesting human-machine collaboration work this last go-around.

I'm in no way official, and I'm known to have a looser opinion of the rules, but to my mind the November part is mostly useful for community, setting a boundary, and giving mutual motivation. There's certainly value in everyone sharing the same month, but I don't see a reason why you shouldn't do an unofficial one whenever you like.

I'd be remiss if I didn't mention that there's an off-season mailing list at https://groups.google.com/forum/#!forum/generativetext and a couple of relevant Slack groups linked to in the Resources thread.

[hendrikboom3]

Well, I guess I'll dedicate June to junogenmo. There's already a junowrimo, so this is probably the right name. See http://www.wikiwrimo.org/wiki/List_of_timed_artistic_challenges#June
July gets a julnowrwimo.

I'll start by reading what others have done over the past few years. Or edit my own landscape generator into presentable form. It's written in Modula 3, which is a rather nice, but hopelessly obscure, programming language (https://en.wikipedia.org/wiki/Modula-3) -- obscure in the sense that few people still know of it, not that it's hard to understand or use.

-- hendrik

[enkiv2]

I would definitely be down with participating in a junogenmo. Should we use this repo or start a new one?

[hendrikboom3]

I'm discussing here because this place is available and there seem to be enough people noticing posts to provide responses and feedback. Even though it's already 2016.

And I found out about the mailing list only after I posted here and started getting feedback.

As to where it should be? Let me know where it ends up. Here would do, except it's already 2016. The new 2016 one which does not exist yet might do too, except it seems traditional to do it in November.

But I don't really care where the crowd agrees to go. As long as I know where.

So far I haven't written a single line of code. I still plan to, and still plan to generate text.

I'm going through the 2015 list of resources and kind of summarizing them. Then perhaps I'll understand what techniques are available -- both mental and implemented. Or maybe I'll have to rearrange and organize them further. The transient hour-by-hour results of this work can be seen at http://topoi.pooq.com/hendrik/nanogenmo/0README.html. Or should I figure out how to start a repo of my own for this text?

Or should I post the summary in one of the wikis, perhaps the original 2013 one, since it doesn't have a date in its name and the information is likely to be viable longterm. Comments on the text welcome. Can be posted here and preserved forever, or emailed to hendrik@topoi.pooq.com, I will revise the text accordingly if I agree and have time.

I have a few ideas for a story, which I suspect will need none of those advanced techniques or tools.

-- hendrik

[enkiv2]

If you start your own repo I'll follow it & post my attempts there.

A lot of people start early or finish late, which makes reusing an old repo
seem questionable if we want to preserve the difference between years.

On Wed, Jun 1, 2016 at 6:48 PM hendrikboom3 notifications@github.com
wrote:

I'm discussing here because this place is available and there seem to be
enough people noticing posts to provide responses and feedback. Even though
it's already 2016.

As tp where it should be? Let me know where it ends up. Here would do,
except it's already 2016. The new 2016 one which does not exist yet might
do too, except it seems traditional to do it in November.

But I don't really care where the crown agrees to go. As long as I know
where.

So far I haven't written a single line of code. I still plan to, and still
plan to generate text.

I'm going through the 2015 list of resources and kind of summarizing them.
Then perhaps I'll understand what techniques are available -- both mental
and implemented. Or maybe I'll have to rearrange and organize them further.
The transient hour-by-hour results of this work can be seen at
http://topoi.pooq.com/hendrik/nanogenmo/0README.html. Or should I figure
out how to start a repo of my own for this text? Or should I post it in one
off the wikis, perhaps the original 2013 one, since it doesn't have a date
in its name and the information is likely to be viable longterm. Comments
on the text welcome. Can be posted here and preserved forever, or emailed
to hendrik@topoi.pooq.com, I will revise the text accordingly if I agree
and have time.

I have a few ideas for a story, which I suspect will need none of those
advanced techniques or tools.

-- hendrik

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#197 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAd6GSwEAd8Badz0wk4ptId-efqswb09ks5qHgxXgaJpZM4IpL5T
.

[hendrikboom3]

OK. I'll have to find out how to start a repo. (I found the instructions. I'll try it tomorrow when I'm not so tired.

Should it be nanogenmo 2016 or junogenmo 2016 for the shared communication space? Having more than one nanogenmo 2016 around might be confusing, even if github can tell them apart because they belong to different people. Or is it OK to create the November one now and start using it already?

Or maybe just call this one nogenmo and use it for any off-season genning? That's appealing.

And I should have an other one for where I develop my own novel generator, as presumably you should too. Or can one repo conveniently hold more than one project? If so I don't know how.

-- hendrik

[enkiv2]

I'd go with junogenmo 2016 only because the november one will probably be
hosted by Darius.

On Wed, Jun 1, 2016 at 8:14 PM hendrikboom3 notifications@github.com
wrote:

OK. I'll have to find out how to start a repo. (I found the instructions.
I'll try it tomorrow when I'm not so tired.

Should it be nanogenmo 2016 or junogenmo 2016 for the shared communication
space? Having more than one nanogenmo 2016 around might be confusing, even
if github can tell them apart because they belong to different people. Or
is it OK to create the November one now and start using it already?

And I should have an other one for where I develop my own novel generator,
as presumably you should too. Or can one repo conveniently hold more than
one project? If so I don't know how.

-- hendrik

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#197 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAd6GSLdLH2rsLeXVv3bA7ZSwjxF7bVYks5qHiBYgaJpZM4IpL5T
.

[hendrikboom3]

I've created https://github.com/hendrikboom3/junogenmo-2016 where people can pose issues to discuss their own off-season projects, and https://github.com/hendrikboom3/Text-generation/ for the development of my own generator

-- hendrik