Re: PLUG vs PDXLUG confusion again

Russell Senior <[email protected]>
Newsgroups gmane.org.user-groups.linux.pdxlug
Message-ID <[email protected]>
>>>>> "Robby" == Robby Russell <[email protected]> writes:

Russell> One, OSCON was recently confused again regarding the proper
Russell> appellation of the PDXLUG group when it apparently (according
Russell> to my sources) allocated an OSCON booth to "PLUG" that
Russell> properly should have been attributed to "PDXLUG" so that you
Russell> get the due credit for your efforts.

Russell> Second, the PDXLUG webpage confusingly calls itself "Portland
Russell> Linux User Group" in the html header title[1].  When this
Russell> subject was last discussed publicly, I got the impression
Russell> that PDXLUG was going to refer to itself as PDXLUG and not as
Russell> "Portland Linux User Group", which is a title that PLUG uses.

Russell> Could the people responsible for talking to OSCON about booth
Russell> space and the webmaster, respectively, please address these
Russell> two issues?

Robby> I'll talk to Matt about fixing the <title> tags for the site.

Thanks.

Robby> Otherwise, what's the point of this thread? 

I don't remember making any other points, just those two.

Robby> We have an OSCON booth and we're going at PDXLUG, [...]

The OSCON people had apparently printed PLUG on a booth assignment
sheet that was actually for PDXLUG, which led to some confusion
amongst third parties.  That confusion got back to me, so I am filing
a bug report.  PLUG at that time didn't even have a booth (I gather
that they are going to be piggybacking on someone elses booth now).

Thanks for helping to address these two issues.


-- 
Russell Senior         ``I have nine fingers; you have ten.''
[email protected]
_______________________________________________
PDXLUG mailing list
[email protected]
http://lists.pdxlug.org/mailman/listinfo/pdxlug
IRC: irc.freenode.net #pdxlug
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.