11:38 p.m.
Hi everyone,
Most of the conversations around and about minishift takes place in the
freenode #minishift channel, we should archive and publish the irc logs, as
it will be usefull for many.
We can dump the logs on github as this is for the minishift community.
Please share your thoughts on this?
--
ANJAN NATH
12:25 a.m.
+1 and if it can be searchable then its a bug winner
On Mon, 29 Jan 2018 at 05:38, Anjan Nath <anjan(a)redhat.com> wrote:
Hi everyone,
Most of the conversations around and about minishift takes place in the
freenode #minishift channel, we should archive and publish the irc logs, as
it will be usefull for many.
We can dump the logs on github as this is for the minishift community.
Please share your thoughts on this?
--
ANJAN NATH
_______________________________________________
Minishift Mailing List mailing list -- minishift(a)lists.minishift.io
To unsubscribe send an email to minishift-leave(a)lists.minishift.io
--
Kamesh Sent from my iPhone, apologises for brevity and typos
12:41 a.m.
On Mon, Jan 29, 2018 at 11:08 AM, Anjan Nath <anjan(a)redhat.com> wrote:
Hi everyone,
Most of the conversations around and about minishift takes place in the
freenode #minishift channel, we should archive and publish the irc logs, as
it will be usefull for many.
We can dump the logs on github as this is for the minishift community.
Please share your thoughts on this?
We have discussed this before and it is a good idea. There are ways to
publish freenode channel logs and I has seen that in some channels like
#gluster . We should should something like that.
-Lala
--
ANJAN NATH
_______________________________________________
Minishift Mailing List mailing list -- minishift(a)lists.minishift.io
To unsubscribe send an email to minishift-leave(a)lists.minishift.io
1:24 a.m.
On Mon, Jan 29, 2018 at 11:08 AM, Anjan Nath <anjan(a)redhat.com> wrote:
Hi everyone,
Most of the conversations around and about minishift takes place in the
freenode #minishift channel, we should archive and publish the irc logs, as
it will be usefull for many.
+1 for archiving.
We can dump the logs on github as this is for the minishift community.
Should be automated process if.
Please share your thoughts on this?
--
ANJAN NATH
_______________________________________________
Minishift Mailing List mailing list -- minishift(a)lists.minishift.io
To unsubscribe send an email to minishift-leave(a)lists.minishift.io
Regards,
Budh Ram Gurung
2:40 a.m.
New subject: Thoughts on archiving/publishing the #minishift irc logs
Hi,
Regarding IRC logging. The plan was to be added to https://botbot.me.
Minikube is there as well as OpenShift. It would be the perfect location.
We are on the waiting list, but it seems the maintainers of the site are not
really active anymore. Maybe it is time to look for another solution.
Obviously there are all integrated solution which do all for you, but in general
logging is trivial for us. Minibot is already logging the chat, the issue is that
we don't have a place to archive the logs. If this could be sorted we can
easily log ourselves.
--Hardy
5:08 a.m.
New subject: Thoughts on archiving/publishing the #minishift irc logs
I was thinking of setting up a IRC bouncer like znc and then upload the
logs to github.
But, since minibot is already seeing #minishift all the time and has the
logs this will be
pretty trivial, I think we can make a script (a cron job that runs in the
same system as minibot)
which pushes the logs daily to a github repo as txt files. We can organize
the logs by having a
_directory_ for the year and inside that directory the logs, where the file
name will be the _date_
for which the log was generated so, one file for each day.
The thing to decide here is, whether having a repo for irc logs in the
minishift namespace sound like
a good or bad idea? Personally since it is for the community there should
be no harm in doing this.
If not then we need to find some other place to dump the logs.
--
ANJAN NATH
6:16 a.m.
New subject: Thoughts on archiving/publishing the #minishift irc logs
Hi,
I was thinking of setting up a IRC bouncer like znc and then upload
the
logs to github.
I don't think pushing to GitHub is a good idea. IMO that is just polluting the
repository. If anything it should go into a dedicaetd repository, but not the
main repo.
Also uploading the logs into a repository still does not give you easy navigation
and searchabilty.
But, since minibot is already seeing #minishift all the time and has
the
logs this will be
pretty trivial, I think we can make a script (a cron job that runs in the
same system as minibot)
which pushes the logs daily to a github repo as txt files. We can organize
the logs by having a
_directory_ for the year and inside that directory the logs, where the file
name will be the _date_
for which the log was generated so, one file for each day.
See above.
If not then we need to find some other place to dump the logs.
That I would think is the preferred solution.
Also, is it really so important?!
--Hardy
6:29 a.m.
New subject: Thoughts on archiving/publishing the #minishift irc logs
I don't think pushing to GitHub is a good idea. IMO that is just
polluting
the
repository. If anything it should go into a dedicaetd repository, but not
the
main repo.
I was thinking of a dedicated repository.
Also uploading the logs into a repository still does not give you easy
navigation
and searchabilty.
Yes, searchability and easy navigation are needed facilities in an irc
log.
> But, since minibot is already seeing #minishift all the time and has the
> logs this will be
> pretty trivial, I think we can make a script (a cron job that runs in the
> same system as minibot)
> which pushes the logs daily to a github repo as txt files. We can
organize
> the logs by having a
> _directory_ for the year and inside that directory the logs, where the
file
> name will be the _date_
> for which the log was generated so, one file for each day.
See above.
> If not then we need to find some other place to dump the logs.
That I would think is the preferred solution.
But where? i can think of github pages
, if we get some fancy jekyll theme with nice readability.
Also, is it really so important?!
I belive its not that important but needed nonetheless or something that is
nice to have, as i often find myself greping
through my local logs for an url someone shared or some error message. I
don't think we will point users to the
channel logs to find information.
--Hardy
_______________________________________________
Minishift Mailing List mailing list -- minishift(a)lists.minishift.io
To unsubscribe send an email to minishift-leave(a)lists.minishift.io
--
ANJAN NATH
7:23 a.m.
New subject: Thoughts on archiving/publishing the #minishift irc logs
Hi,
> I don't think pushing to GitHub is a good idea. IMO that is
just polluting
> the
> repository. If anything it should go into a dedicaetd repository, but not
> the
> main repo.
>
I was thinking of a dedicated repository.
Right, I would assume this as a minimum requirement.
But do you really want to log everything or just say the standup or other meetings?
Within Hibernate we only logged meetings which seems more appropriate.
I am just a bit wary about all the useless information which would be persisted.
If you often end up having to extract valuable information from the IRC channel,
maybe another problem should be addressed. For example, if the information is related
to an issue and how to address it, I recommend pasting the relevant messages as a
comment on the issue.
If there was a general useful piece of information, why not post it to the mailing list.
Maybe someone else has use for it as well. Overall I find the mailing list underused.
I would think a lot of discussions would benefit from being taken off IRC and onto the
mailing list.
Having to grep IRC logs feels like a terrible waste of time to find information.
> That I would think is the preferred solution.
>
But where? i can think of github pages
, if we get some fancy jekyll theme with nice readability.
Sure. Possible. There is also Gollum which would work quite nicely. Note though,
one needs to put some development effort into it. Even though not hard, one will
need to extend Minibot. Next you need to sort out if and how to address searchability,
etc.
botbot.me would have been the ideal solution since it would have required no effort from
our side.
> Also, is it really so important?!
>
I belive its not that important but needed nonetheless or something that is
nice to have,
See above. Look, I am playing devil's advocate here.
--Hardy
7:33 a.m.
New subject: Thoughts on archiving/publishing the #minishift irc logs
Meetings only... pretty much like fedbot/zodbot does.
3:19 a.m.
New subject: Thoughts on archiving/publishing the #minishift irc logs
Hi,
Meetings only... pretty much like fedbot/zodbot does.
That would be my idea as well. In this case I would then wonder whether it would not
make more sense to send the standup/meeting logs to the mailing list (something the
Hibernate
projects do as well. The weekly meeting protocol gets sent to the Hibernate mailing
list).
In this case we don't have to create a new repo and get archiving and search for free.
Also we probably reach a wider audience.
There is https://github.com/minishift/minibot/issues/38 which talks about introducing a
meeting
plugin. Effectively this is the same as the standup with some additional bells and
whistles.
The ongoing meeting is logged into the Minibot Reddis brain and at completion of the
meeting,
the protocol gets send out to the mailing list (preferably with a list of action items,
see also
the JBoss meeting bot).
If one also want to send out the standup logs, that's pretty much ready to go. All one
needs is
to setup and configure the ability to mail out the protocol (whether the standup protocol
should
really be mailed out might be debatable).
Overall one looks at a couple of days work (maybe a bit more if one is not familiar with
the bot
and CoffeeScript).
IMO creating and setting up this type of meeting bot would be ore valuable than blindly
archiving
IRC logs.
--Hardy
1579
days inactive
1580
days old
10 comments
7 participants
participants (7)
-
Anjan Nath -
Anjan Nath -
Budh Ram Gurung -
Gerard Braad -
Hardy Ferentschik -
Kamesh Sampath -
Lalatendu Mohanty